Interactive gratuity platform

ABSTRACT

In some examples, methods and systems generate interactive receipts with the option of a dynamic tip amount. The method includes determining at least one tip determinant based at least in part on the payment transaction, wherein the tip determinant is selected from a group of: the merchant; the customer; a payment object presented by the customer towards the payment transaction; a geographical location of a mobile device associated with one of the merchant and the customer; and a category of a merchant&#39;s item corresponding to the payment transaction. The method includes obtaining, by a dynamic tip generator, a tipping profile based on a history of tipping behavior associated with the tip determinant and generating, by the dynamic tip generator, at least one dynamic tip amount based at least on the tipping profile, which is presented to the customer.

PRIORITY

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 16/859,639, filed on Apr. 27, 2020, whichclaims priority to U.S. patent application Ser. No. 15/087,960, filed onMar. 31, 2016, entitled “INTERACTIVE GRATUITY PLATFORM”, now known asU.S. Pat. No. 10,636,019, issued on Apr. 28, 2020, which is fullyincorporated by reference herein.

TECHNICAL FIELD

Customers are generally provided with paper receipts of the transactionat the point-of-sale (POS) terminal as proof of purchase ofgoods/services. The receipt generally includes an itemization of theproduct or service and a total net cost of all the products and/orservices. The paper receipt serves as a proof of the purchase for thecustomer. Some merchants have started to provide their customers withreceipts electronically to maintain record of the financialtransactions. For example, some merchants may provide a receipt throughdelivery of an electronic mail (i.e., e-mail).

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features. Moreover, multiple instances of the samepart are designated by a common prefix separated from the instancenumber by a dash. The drawings are not to scale.

FIG. 1A is an example architecture of payment processing system forenabling point-of-sale (POS) transactions between merchants andcustomers and generating receipts in response to the POS transactionwith the option of adaptive tipping, according to an embodiment of thepresent subject matter.

FIG. 1B illustrates a first embodiment of an interactive digital receipttechnique implemented on a customer device.

FIGS. 1C-1E illustrate a second embodiment of an interactive digitalreceipt technique implemented on a customer device.

FIGS. 1F-1H illustrate a third embodiment of an interactive digitalreceipt technique implemented on a customer device.

FIG. 1I illustrates a fourth embodiment of an interactive digitalreceipt technique implemented on a customer device.

FIG. 2 illustrates a flow diagram of a process for generating an dynamictip amount and implementing the tipping feature on an interactivedigital receipt technique on a customer device, according to anembodiment of the present subject matter.

FIG. 3 illustrates a screenshot of a gratuity dashboard for managinginteractive digital receipts implemented on a customer device, accordingto an embodiment of the present subject matter.

FIG. 4 illustrates a screenshot of a gratuity dashboard for managingmerchant engagements with customers, according to an embodiment of thepresent subject matter.

FIGS. 5A and 5B are sequence diagrams illustrating the operations of tipgeneration in an offline, open-ticket scenario, according to anembodiment of the present subject matter.

FIGS. 6A and 6B are flow diagrams illustrating an example process forhandling tipping in offline mode for example in the context of openticket transactions, according to an embodiment of the present subjectmatter.

FIG. 7 is a block diagram illustrating components of a paymentprocessing system, according to an embodiment of the present subjectmatter.

DETAILED DESCRIPTION

Introduced herein is a technique to provide an interactive digitalreceipt implemented on a customer device, where the receipt offers aninteractive platform for merchants and customers to interact on acontinuous basis. More specifically, the interactive digital receiptincludes an interactive component that generates adaptive tip amountscorresponding to a merchant behavior, customer behavior, or the natureof items in a shopping cart. The interactive digital receipt can beembodied in a text message, an electronic mail (e-mail), or a mobilesoftware application. The interactive digital receipt is generated inresponse to an occurrence of a particular financial transaction betweena merchant and a customer, such as a payment transaction conducted at acompletion of service and/or goods provided by the merchant. Thefinancial transaction may be an electronic transaction conducted overthe Internet or a card present point-of-sale (POS) transaction where thecustomer/buyer/payer makes the purchase at a store front, other“brick-and-mortar” location, or simply in the presence of amerchant/payee.

Once the financial transaction takes place (i.e., the payer tenderspayment to the payee), the interactive digital receipt is generated toprovide the customer with an electronic record of the transaction. Inaddition to providing the transaction record, the interactive digitalreceipt provides one or more tools for customer engagement, orinteractive components, to enable the merchant and the customer toengage, or interact, with one another. Such interactive components maybe time-based thus allowing the engagements, or the interactions, totake place only until the expiration of the time period.

In some instances, the disclosed technique provides an engagementcomponent that includes a gratuity payment feature to allow the merchantto generate an adaptive gratuity amount (i.e., “tip”) on top of apayment amount for a purchase from a particular merchant. The gratuitypayment feature allows the customer to tip the merchant after the timeof the actual transaction. The gratuity payment feature can be providedbefore or after displaying the payment amount. While displaying beforeremoves bias in tipping, displaying after allows the customer to havemore control on their tipping behavior. In some implementations, thegratuity payment feature also allows the customer to add or modify theadaptive gratuity amount generated by the engagement component.

The merchant may set the time limit at which the interactive receipt(for the purchase) is open for receiving the gratuity amount from thecustomer. The customer may set a nominal gratuity amount to operate as adefault amount to be paid to the merchant if no gratuity is added aftera predefined time limit. For example, such nominal gratuity amount maybe set for a particular favorite merchant of the customer; that is, thecustomer desires to always tip a nominal amount even he/she forgets toadd such amount after a transaction. The gratuity payment feature isbeneficial, for example, when the customer has forgotten to tip anddesires to tip after he/she has already made the payment and left themerchant's store. The nominal gratuity amount may also be set by themerchant. This is beneficial in scenarios involving special servicesand/or goods. For example, a restaurant merchant sets a default 25% tipfor any transaction involving 10 or more parties dining at therestaurant, or to adjust the tip on the nature of items in the cart bycharging higher tips on non-perishable goods and no tips on others.

In some instances, the disclosed technique provides an engagementcomponent that includes a feedback feature to allow the customer to seta condition or rule for subsequent transaction. The condition can bemapped to the gratuity amount thus automatically adjusting the gratuityamount when the condition is met. For example, the customer may set thecondition such as modify the gratuity amount to be adapted based solelyon the cart value and not on any other factors. Such condition may thenbe applied to transactions. The feedback feature also allows thecustomer to leave a review (e.g., a write-up, a rating, etc.) for aparticular merchant after a transaction is completed. The feedbackfeature is offered to the customer within a predefined time period. Themerchant may configure the predefined time period. For example, the timeperiod can be an hour, a day, or a week after a payment transaction(e.g., a restaurant visit) has completed. The merchant may configure thepredefined time period to be tied to an incentive. For example, thecustomer is rewarded a 20% Off Coupon via the interactive receipt forsubmitting a condition within an hour of the transaction completiontime. Such time-based feedback feature is beneficial, for example, whenthe merchant wants to improve the dataset that generates adaptivegratuity amounts and configure the tip amounts more increase visibilityof the merchant venue (i.e., through reviews), to incentivize thecustomer to act more quickly in submitting the feedback, and/or tomanage the collection of feedback more effectively and in a timelymanner (e.g., allowing a review six days after the service is likelyineffective).

In some instances, the disclosed technique provides a particularcustomer an interactive transaction record containing all interactivedigital receipts of transactions between the particular customer and oneor more merchants. The transaction record also includes interactivedigital receipts corresponding to all transactions with a mapping of tipwith item on a particular receipt, in case the tip varies on a per-itembasis. The interactive transaction record organizes the interactivedigital receipts based on time, location, and merchant. The interactivetransaction record is updated along with each new interactive digitalreceipt that gets generated and or updated. Further, the interactivetransaction record allows the customer to access each interactivedigital receipt. This can be beneficial when the customer wants torevisit a record for a particular transaction. For example, if acustomer wants to review and add a gratuity amount to a paymenttransaction completed recently, he or she can access the interactivetransaction record to search for the particular transaction and add on atip to the payment authorization for that transaction.

In some instances, the disclosed technique provides a customer interfacefor a particular merchant to configure various engagements that may beoffered via the interactive digital receipts on the customer devices ofone or more customers. In some instances, the interface allows themerchant to create one or more customized templates for the interactivedigital receipts of particular customers. As such, the disclosedtechnique allows the merchant to dynamically change what is beingoffered, or displayed, on the customer device of the frequent customer.

The systems and methods described herein disclose various methods andsystems that give the merchants and customers more control andgranularity in selecting tips. Traditionally, the gratuity amounts arefixed based on the payment amount and are generally a percentage of thepayment amount. Imagine performing transactions in businesses thatespecially require the customer to react quickly. For example, at acoffee shop during peak hours or in a cab. In such scenarios, it hasbeen shown that giving customers quick tip options to pick from is moreefficient than letting them key-in a gratuity amount. For example, themerchants are known to keep the tip amounts at fixed percentages of 10,15, 20, 25, and so on. While fixed percentages work for some products orservices, a more granular tip amount selection is desired. For example,in many of the city's cabs, riders are offered options for their tipdepending on the length of the ride. For fares under $15, a screenprompts tips of $2, $3 or $4; the numbers can range from 15 percent to30 percent for higher fares. The presets are used about 70 percent ofthe time, according to industry estimates.

This analysis is particularly true with the rise of use of credit cards,which has become a convenient payment method not just for longer trips,such as the area's airports, but also for shorter, cheaper rides, thetype of $5 rainy-day indulgences that were once handled exclusively withcash. At the end of 2008, about one-fifth of cab rides were being paidfor with a card. That portion has grown steadily in 2009-10, reaching 28percent. Meanwhile, black-car business has fallen about 30 percent, ascompanies encourage employees to use corporate credit cards to expensecheaper yellow-cab rides.

Thus, while the credit card use is increasing, the gratuity amounts havemostly stayed static or preset. Research shows that the average tipgenerally comes out to just over 18 percent. The preset tip amounts areused more than half the time, resulting in a $5.30 ride getting a tip of$2, or about 38 percent. Due to such set-ups, the customer either paysno tips at all or overly excessive tips.

To this end, as disclosed herein, the interactive gratuity paymentfeature is generated based on the analysis of the seller and customerbehavior over a period of time and generates gratuity amounts that aremore in accordance with their behaviors instead of static values. As aresult, the customer is more likely to select tips instead of leavingno-tips. From the customer's perspective, the customer selects tips thatwork with their budget and preferences making it easier to tip evenduring rush hours. The systems and methods described herein can offernew and efficient channels to generate revenue from tip amounts andcirculate to other aspects of business, thus effectively creatinganother avenue for revenue generation. The tip can be used to furtherstrengthen the specific merchant-customer relationship, for example,higher tips may lead to coupons and rewards or better service insubsequent interaction with the high-tipping customer. The tippingfeature can be either interactive or static. Further, the tippingfeature allows granularity and flexibility in tipping. In someimplementations, the tipping is based on the category of item, locationof the merchant's store, and card-linked purchases or tipping history.The tipping score or profile can also be an aggregate of multiplebehaviors collected over time and combined on the basis of a weightingscale or randomly.

The interactive receipt as disclosed herein can be designed to interactwith the customer, for example, by allowing the customer to followhyperlinks, embedded webpages, enter information in fields for furtherprocessing, share on social networks or other communication networks.The systems and methods set the default options on a per-transactionbasis, based on a number of inputs. For example, if the PPS recognizesthe payment instrument (in most markets the swipe, dip, or tap happensbefore the tip is selected), the PPS can detect the buyer's overalltipping behavior—whether they are a high or low tipper. Do they usuallytip the middle option? When if ever do they select a custom tip? The PPSalso includes a history for the seller. Many sellers “set and forget”their tip options, but PPS can look at how their tip options areperforming, and compare that to other sellers, perhaps in similarbusinesses, geographies, etc. Also, PPS evaluates the items in thecart—that is, what items are part of this purchase. Tipping behavior canvary based not just on the buyer and seller, but also on what is beingpurchased.

The present subject matter can operate in both real-time and offlinemodes. Embodiments of the present subject matter are configured tooperate regardless of the kind of mobile device, web applications,mobile applications, POS topologies, payment cards, computer networks,and environments. Embodiments of the present subject matter may findvarious applications in, e.g., coin and non-coin based point of sale(POS) systems where receipts are generally provided to itemizepurchases. Furthermore, transactions on such POS systems may be eitherdirect or remote.

Various embodiments and implementations of the disclosed paymenttechnology are now described. The following description providesspecific details for a thorough understanding and an enablingdescription of these implementations. One skilled in the art willunderstand, however, that the disclosed system and methods may bepracticed without many of these details. Additionally, some well-knownstructures or functions may not be shown or described in detail, so asto avoid unnecessarily obscuring the relevant description of the variousimplementations. The terminology used in the description presented belowis intended to be interpreted in its broadest reasonable manner, eventhough it is being used in conjunction with a detailed description ofcertain specific implementations of the disclosed system and methods.Some frequently used terms are now described.

As used herein, a merchant may include any business engaged in theoffering of goods or services for acquisition by buyers. Actionsattributed to a merchant may include actions performed by owners,employees, or other agents of the merchant and thus no distinction ismade herein unless specifically discussed. In addition, as used herein,a customer or buyer may include any entity that acquires goods orservices from a merchant, such as by purchasing, renting, leasing,borrowing, licensing, or the like. Hereinafter, goods and/or servicesoffered by merchants may be referred to as items. Thus, a merchant and abuyer may interact with each other to conduct a transaction in which thebuyer acquires an item from a merchant, and in return, the buyerprovides payment to the merchant, for example through a payment object.

As used herein, a ‘payment transaction’ or simply ‘transaction’ mayinclude a financial transaction for the acquisition of goods and/orservices that is conducted between a buyer and a merchant. For example,when paying for a transaction, the buyer can provide the amount that isdue to the merchant using a payment object or even a payment proxy. Inother cases, the payment transaction includes transfer of money from oneparty to another for any number of reasons. Thus, while the descriptionrefers to as buyer and merchant as parties to the payment transaction,it will be understood that the parties can be a sender and a recipient,a land lord and a renter, a bank and a bank customer, a first friend anda second friend, and so on.

The term ‘payment card’ or ‘payment object’ refers to a paymentmechanism that includes a conventional debit card, a conventional creditcard, a prepaid gift card, or the like, a smartcard that has an embeddedintegrate circuit chip (e.g., Europay-MasterCard-visa (EMV) card), aproxy card, or any card that functions as a combination of any of thesemechanisms. The term ‘proxy card’ as used herein refers to a card thatmay or may not bear a card number or an account number that appears tobe that of a real credit or debit card account (i.e., it is in thecorrect format), but where that card/account number is actually only aproxy for the buyer's real card/account number. Additionally, thepayment card used in the example above is a specific type of a financialinstrument. Other types of financial instruments, other than the paymentcard, can be used to initiate the transfer of funds. A financialinstrument can be a software instrument or virtual instrument, such as avirtual wallet. Other examples of payment card may also include aprepaid card, a gift card, a rewards card, a loyalty points' card, afrequent flyer miles card, a check, cash, or any other kind of paymentobject that holds financial value or provides a promise to pay at alater time. Payment card may also include a payment object, such as anelectronic device configured to initiate contactless paymenttransactions, e.g., a key fob, a mobile device (such as a mobile devicehaving an NFC tag). And finally, the payment object can also be apayment proxy having a syntax of a monetary indicator followed by astring of alphanumeric characters or in general, any identifier that isrepresentative of the buyer or merchant's financial account. The paymentproxy can be used in the context of and within a webpage as part of theweb address, a social networking handle or customer name, a forum, amessaging application, and so on. The payment proxy can also be abiometric payment object.

The term ‘biometric payment object’ is a type of payment object orfinancial instrument that is biometrically identifiable and initializedby a biometric characteristic, such as a person's finger (e.g., forfingerprint recognition), face, iris or retina, heartbeat, voice, etc.

The term “landing page,” as used here, refers to a virtual locationidentified by a personalized location address that is dedicated tocollect payments on behalf of a recipient associated with thepersonalized location address. The personalized location address caninclude the payment proxy discussed above. In some embodiments, thelanding page is identified by a uniform resource locator (URL) thatincludes a payment proxy, where the URL is accessible through a webbrowser application installed on a client device of the sender. Forexample, the URL is www....com/$charityName. In another example, the URLis www....com/$aaron. In some embodiments, the landing page isidentified by a graphical customer interface (GUI) of a mobile paymentapplication installed on a client device of the sender. For example, theGUI of the mobile payment application is dedicated to $charityName,where there can be multiple GUIs each dedicated to a different paymentproxy.

The landing page is generated by the payment processing system toreceive, e.g., collect, one or more payments on behalf of the recipientfrom one or more senders. The sender can access the landing page, e.g.,by entering a URL into a web browsing application installed on thesender's client device. Upon navigating to the URL, the sender cansimply enter a payment amount, e.g., in a web form field, and send themoney, e.g., by selecting a “Pay” action button displayed on thewebsite. In another example, the sender can access the landing page,e.g., by selecting a GUI within a mobile payment processing systemapplication, where the GUI, e.g., is labeled with the payment proxy$aaron. The sender can further enter a payment amount at the GUI andsend the money, e.g., by selecting a “Pay” action button displayed onthe GUI.

The term “forum,” as used here, refers to a media channel (e.g., asocial networking website, a microblog, a blog, etc.) that enablescustomer interaction and engagement through comments, posts, and/ormessages. The forum can be employed by a service provider to providevarious services to customers of the forum, e.g., create messages, postcomments, interact with one another, etc. Within a forum context, acustomer can indicate an intent to transfer money by specifying apayment proxy in a message that the customer submits, e.g., “posts,” ona particular forum, where that payment proxy carries the syntax of themonetary indicator preceding one or more alphanumeric characters. Forexample, the customer posts a message “I support $funnyguy311 with $10.”In such an example, the payment processing system detects the customer'sintent to send money, e.g., $10, to “$funnyguy311” and initiates thetransfer of money upon identification of a recipient financial accountassociated with “$funnyguy311.” The monetary indicator can correspond tovarious currencies, e.g., dollar ($), euro (€), pound (£), yuan (¥),etc. Although use of the dollar monetary indicator ($) is used herein,it is to be understood that any currency symbol could equally be used.

The term “merchant application,” “registration application” or “mobilepayment portal” as used here, refers to any messaging application thatenables communication between customers (e.g., sender and recipient of amessage) over a wired or wireless communications network. A serviceprovider that delivers a communication service to customers, e.g., chatcapability, can employ the messaging application. The messagingapplication can include, for example, a text messaging application forcommunication between phones (e.g., conventional mobile telephones orsmartphones), or a cross-platform instant messaging application forsmartphones and phones that use the Internet for communication. Within amessaging application context, a customer can indicate an intent totransfer money by specifying a payment proxy in a TO field of, e.g., amessage, that the customer inputs within the messaging application. Forexample, the customer enters into the TO field “$redcross.” In anotherexample, the customer enters into the TO field “$aaron.” Once thecustomer enters a payment proxy, or input, into the TO field, thecustomer can enter a message in a body of the message, e.g., “Here is$10,” and send the message. In various embodiments, the message can be atext message, a chat message, an email message, or indeed any other typeof message that is capable of being exchanged between computing devices.Although this specification may employ text messages as an example, itis to be understood that the payment proxy technology may employ any ofthese types of messages. Upon receiving an indication to send (e.g.,after detecting that the customer has clicked “Send”), the messagingapplication transmits a message, e.g., the text message to a messagingapplication computer system (“messaging application system”). Themessaging application system detects that the input in the TO field ofthe message it has received includes a syntax of a monetary indicatorpreceding one or more alphanumeric characters. In response, themessaging application system forwards the text message to the paymentprocessing system for processing. The payment processing systemidentifies a recipient associated with the input (or payment proxy) thatis derived from the TO field, and further identifies a recipientfinancial account associated with that recipient. Upon identification ofthe recipient financial account, the payment processing system initiatesthe transfer of money.

With a number of cardholder payment options (e.g., magnetic stripe,contact chip and contactless chip) and methods in development (e.g.,mobile and cloud-based), the card issuing institutions bake variouskinds of information in the payment object. This information includes acard number, an expiry date, a point-of-sale entry code, and a servicecode. A card number is a sequence of digits that identifies a bank thatissued the credit card and an account number that is specific to thecardholder. In some circumstances, a card number is also referred to asa “primary account number” (PAN). An expiry date of a credit cardindicates a date when the credit card expires. A service code of acredit card indicates how the cardholder is permitted to use the creditcard, and also whether the card includes a magnetic stripe or anintegrated circuit with dynamic card information embedded therein. Thepoint-of-sale entry code indicates how the card is introduced in a cardreader, that is whether it is swiped or dipped.

It is noted that the payment technology is equally applicable in otherembodiments to various other content providers and various other typesof providers, such as financial service providers or to any applicationthat involves communication of messages between customers, and that thepayment technology is not limited to a specific application, device orindustry.

The preceding summary is provided for the purposes of summarizing someexemplary embodiments to provide a basic understanding of aspects of thesubject matter described herein. Accordingly, the above-describedfeatures are merely examples and should not be construed as limiting inany way. Other features, aspects, and advantages of the subject matterdescribed herein will become apparent from the following description ofFigures and Claims.

Turning now to the Figures, FIG. 1A is an example architecture ofinteractive receipt generation 150 for enabling point-of-sale (POS)transactions between merchants 152A and customers 152B and providing atipping option that is granular and adaptive to the customer performingthe transaction. In the example of FIG. 1A, the interactive receiptgeneration system 150 includes a POS terminal 154 (associated with amerchant 152A) executing an instance of a merchant application 156 and aplurality of payment object readers, such as a magstripe object reader108 and an EMV object reader 158 connected to the POS terminal 154. Thesystem 150 further includes a payment processing system 164 (“PPS 164”),and one or more bank computing device(s), an issuer of the paymentobject, and an object payment network computing device(s) (not shown);all of which are connected via a communications network(s) 184,according to an embodiment of the present subject matter.

The environment 150 includes the PPS 164, a customer 152B associatedwith a customer device 160, a POS terminal 154 associated with a paymentobject reader 158 being operated by a merchant 152A, in which thecustomer 152B introduces a payment object 162 to pay for a product orservice (“item”) offered by the merchant 152A.

As illustrated in FIG. 1A, the payment processing system (PPS 164 isoperatively coupled, via a network 184, to the customer device 160 andthe POS terminal 154. In this way, the payment processing system 164 cansend and receive information, to and from the POS terminal 154 and thecustomer device 160, to facilitate generating an interactive digitalreceipt for one or more financial transactions between the merchant andthe customer. It is noted that FIG. 1A illustrates only one example ofan embodiment of the environment 120, and it will be appreciated that inother embodiments, the environment may include more or fewer componentsand that the components may have a different configuration. Further, thevarious components shown in FIG. 1A may be implemented by usinghardware, software, firmware or a combination thereof, including one ormore signal processing and/or application specific integrated circuits.

The customer 152B can use any of a variety of payment objects 162, suchas credit cards, debit cards, etc., when participating in POStransaction with a merchant 152A. In some embodiments, payment objects162 can include one or more magnetic stripes with customer financialinformation stored thereon. The data can be read when the magneticstripes are swiped in a payment object reader 158 communicativelycoupled to POS terminal 154. In some embodiments, other types of paymentobjects 162 can be used, for example smart cards having a built inintegrated circuit including a memory chip (e.g. EMV payment objects), aradio frequency identification tag (e.g. near field communicationenabled objects), and the like. For this, the payment object reader 158obtains data off the EMV chip on the payment object 162. In someexamples, the payment object 162 includes EMV chip and also magstripesto allow backward compatibility with legacy readers.

Referring to FIG. 1A, the network 184 may be a communication networkbased on certain communication protocols, such as TCP/IP protocol. Suchnetwork may include, but is not limited to, Internet, Intranet, widearea network (WAN), local area network (LAN), wireless network,Bluetooth, WiFi, and mobile communication network. The physicalconnections of the network and the communication protocols are wellknown to those of skill in the art.

The customer device 160 may be, for example, mobile devices andcomputing devices that can communicate with the PPS 164 and the POSterminal 154 through the network 608. The customer device 160 can be theuser device 100 of FIGS. 1B-1I. The customer device can include amerchant application 156 or an instance thereof.

The POS terminal 154 may be, for example, mobile devices and computingdevices that can communicate with the PPS 164 and the customer device160 through the network 184. The mobile devices include, but are notlimited to, smartphones (e.g., Android®-enabled phones), personaldigital assistants (PDAs), portable computers with wired or wirelesswide-area-network and/or telecommunication capability such as tabletpersonal computers and “netbook” personal computers. The computingdevices include, but are not limited to, personal computers, electronicpoint-of-sale cash registry machines, and electronic kiosks. The POSterminal 154 can be the user device 100 of FIGS. 1B-1I. The POS terminal154 too can include the merchant application 156 or an instance thereof.The payment processing system 164 includes a processor 166,communications circuitry and an input/output interface (not shown), anda memory 168. These components may be coupled by one or morecommunication buses or other signal lines. It is noted that the system164 can include more or fewer components.

The processor 166 includes one or more processors. The processor 166 isoperatively coupled to the communication circuitry and the memory 168.The processor 166 may include a digital signal processor, amicroprocessor, and various analog-to-digital converters,digital-to-analog converters, and other support circuits and/orcombinations thereof. The processor may be configured to executecomputer/machine readable and executable instructions stored in thelocal memory 168 or in a remote device memory (not shown). Suchinstructions are implemented by the processor 166 to perform one or morefunctions described above. In performing such functions, the processor166 uses the communication circuitry to communicate with the network 184and other devices on the network 184, such as the POS terminal 154 andthe customer device 160.

The memory 168 includes one or more memories. The one or more memoriesmay be, for example, cache memory, main memory and secondary memory. Thememory 168 includes computer-readable instructions 169, where thecomputer-readable instructions may be executed by the processor 166 toimplement a mobile application on the customer device 160, such as aninteractive digital receipt application. In some embodiments, the memory168 may include data storage (not shown) for storing data created and/orused by to the interactive digital receipt application.

The memory 168 may include components, such as mapping component 170,dynamic tip generator 172, the POS component 171, the patternrecognition component 174, and the exception handler 176. The memory 168also includes data tables such as buyer or merchant data, user orcustomer data, card or payment object data, item data, location data,tipping profile, open tickets, and also tipping weight 182 andconditions 180.

Operationally, a customer 152B approaches a payment object reader 158and requests an item, which can be a product or service. The POScomponent 171 of the PPS 164 can generate the user interface for themerchant 152A to select the items requested by the customer 152B. ThePOS component 171 can also open an existing open ticket or tabpreviously generated by the merchant. In response, the customer providesa payment object which the merchant inserts, swipes, taps or otherwiseintroduces the payment object 162 in the reader 158, the reader 158registers it as a transaction activity. The reader 158 reads the dataoff of the payment object 162 and encrypts the data as transaction data.The reader then transfers the encrypted data to the POS terminal 154. Insome cases, the POS terminal 154 receives unencrypted data from thereader 158. If the customer is using a merchant application 156 toperform an online transaction, the transaction data includes the deviceidentifier, e.g., IP address or other kind of device fingerprint.

The transaction data also includes other information such as location ofthe customer, merchant or the devices associated with the customer andthe merchant, or the location with respect to the merchant's store. Thepayment object reader 158 proceeds to detecting entry of the customer ormerchant device through location detection techniques, such astechniques based on angulation, lateration, proximity detection, deadreckoning, geo-fence, global or local positioning systems, BluetoothTechnology, Near-Field Communication Technology, sensors-basedtechnology, Radio frequency identification (RFID) system, or the like.In one embodiment, the reader 158 can establish an automatic geo-fenceand entry and exit of the devices tracks location of the devices.According to the present subject matter, the geo-fence is defined andestablished based on a current location of an asset, for example usingGPS data comprising latitude and longitude along with some predeterminedarea based on range or distance. In this manner, the user need notmanually specify a location by drawing a perimeter, specifying a pointlocation, or by any other means.

The transaction data can also include card data such as service codes,point of entry codes, card verification values, last four of the cardetc. Also, item data such as category of items, quantity of items andnature of items for example, whether they are perishable or frozen, canbe tracked in the transaction data. The items may be in a shopping cartin a single or batch payment transactions.

The transaction data can also include merchant or customer identifiers,for example, a person's fingerprint, face, iris or retina, etc., or ingeneral, hand characteristics, eye characteristics, facialcharacteristics, and voice characteristics. The other identifiersinclude social security number, driver's license number, passportnumber, and the like.

The POS terminal 154 or the reader 158 sends the transaction data to thePPS 164. The PPS 164, through the POS component 171, analyzes thetransaction data to extract tip determinants. The tip determinantsidentify the merchant, customer, customer location, merchant location,item type, payment objects, and the like, shown as buyer data, merchantdata, card data, item data, location data, open tickets in the figure.

The PPS 164 then maps the tip determinants to any data, for examplehistory of transactions, stored in the database 178 through a mappingcomponent 170. For example, the card data can be used to track any otherpurchases made on that card and the tipping history thereof. The buyerdata, similarly, can be used to determine the past purchases and tippinghistory of the customer or even by other customers in the neighborhoodof the merchant or customers purchasing similar items. The item data canbe used to determine tipping history associated with a specific item.For example, it may be determined that a coffee is likely to be tippedat 10% than a food item, like a sandwich. In some cases, the tipdeterminants and their tipping behaviors can be cross-mapped, whichmeans once the buyer data has been mapped to tipping history, thetipping history can be further analyzed to see how the customer tips acertain item or merchant, or if there are any preferences to a certainday. For example, the customer may be more likely to tip more onweekdays. The mapping component 171 may be based on probabilisticmapping algorithm, tree search algorithm, brute-force search algorithms,combinatorial search algorithms, minimax algorithm, alpha-beta pruning,Informational search and the A* algorithm, among others. The patternrecognition component 174 can analyze data from the mapping component171, such as historical tipping behaviors associated with the tippingdeterminants to identify patterns, if any. For example, a customer mayhave a habit of leaving no tip in cabs, whereas tipping may be moreprominent in restaurants. The pattern recognition component 174 cancreate a rule or condition 180 as a result of this analysis. In otherimplementations, the pattern recognition component 174 cancross-reference this with other fringe details, such as the timeavailable to enter tip, to better understand whether the customer islikely to pay in less-rush scenarios.

Once the tipping behaviors corresponding to the tip determinants areobtained, the dynamic tip generator 172 generates a tipping profilebased on a unique combination of tip determinants obtained off thetransaction data at the time of transaction, or a single tip determinantrandomly selected from the obtained tip determinants. In some cases, allor some tip determinants may be used. The order of tip determinants orthe hierarchy of tip determinants can be stored in “weights plane.” Thetipping profile can be an algorithm, a mathematical relationship, afixed value or a range of values of gratuities or tips that the customergenerally tips. The profile is specific to the transaction, and is inpart based on the items in the cart.

In some cases, the tipping profile may be based on conditions 180. Theconditions 180 are set by the PPS 164, merchants or customers. Once thetipping profile is generated, the dynamic tip generator sends theassociated tip values or ranges to the merchant application 156 for thecustomer to choose from as part of the tipping feature in an interactivereceipt. In some cases, the tipping feature is generated before thecustomer provides authorization of credit transaction and in some cases,it is provided after the customer finalizes the transaction. It will beunderstood that while some implementations may specifically relate tophysical stores, the present subject matter can apply the interactivereceipts with the tipping feature for online scenarios as well.

In some implementations, the dynamic tip generator 172 generates a tipvalue generally provided by customers in the neighborhood of themerchant or for such items. This value may be a fixed 10, 20, 25%, etc.The dynamic tip generator then adjusts this value based on the tippingprofile. Such differences, that is between what the static value was andthe one generated by the tipping profile is displayed by the PPS ontothe POS terminal. In some implementations, the customer can choose toselect the static value which is controlled and maintained by theexception handler 176.

Referring to FIG. 1B, which illustrates a first embodiment of aninteractive digital receipt technique implemented on a customer device100. As used herein, the term “customer device” refers to anygeneral-purpose computing device capable of data processing. In oneexample, the customer device can be a mobile device, such as asmartphone (e.g., iPhone®, Android®-enabled phone, etc.), a personaldigital assistant (PDA), a tablet, an e-reader, or other mobile orportable computing devices. In another example, the customer device canbe a personal computing device, such as a desktop, a laptop, or otherwired and wireless personal computers. The customer device 100 isequipped with a display screen 102 for displaying various customerinterfaces to enable a customer to interact with content generated bythe customer device 100.

The customer device 100 can implement an application, such as aninteractive receipt mobile application for use by a mobile customer,where the interactive receipt mobile application includes one or morecustomer interface components. As used herein, a “customer interfacecomponent” is a component of a customer interface intended for acustomer to view and interact with an interactive digital receipt 104.The interactive digital receipt 104 is generated for the customer afteran occurrence of a financial transaction between the customer and amerchant (e.g., payment that occurs at the completion of a serviceand/or tendering of goods), where the interactive digital receipt 104 isdisplayed on the display screen 102 of the customer device 100. It isnoted that the interactive digital receipt 104 may take up an entiretyor any portion of the display screen 102. The interactive digitalreceipt 104 includes various interactive components, such as a customertransaction interface component 106 (“transaction component”) and one ormore customer engagement interface components 108 (“engagementcomponent”). The transaction component 106 displays details associatedwith a particular transaction between the customer and the merchant,where the transaction details are displayed in real time in response toan occurrence of the particular transaction (e.g., payment transactionat the completion of a service). For example, when the customer has madea payment to the merchant, the interactive digital receipt isautomatically generated on the customer device 100, and included on thereceipt are details of the purchased items and prices generated by thetransaction component 106.

The one or more engagement components 108 displays in real time one ormore features for the merchant and the customer to interact or engagewith one another. In one implementation, the features generated areconfigured to be available via the interactive digital receipt onlywithin a predefined time period. The predefined time period isconfigurable by the merchant and allows the merchant to providetime-based incentives to engage the customer to interact with themerchant. In other implementations, the features generated can beaccessed at anytime. Further details regarding the engagement componentsand the transaction component will be discussed in FIGS. 1C-1H.

FIGS. 1C-1E illustrate a second embodiment of an interactive digitalreceipt technique implemented on a customer device 100. As illustratedin FIG. 1C, the interactive digital receipt 104 includes an engagement,or interactive, component for generating a tipping feature 110. Thetipping feature 110 allows the customer the option to select or even adda gratuity amount (i.e., “tip”) after the occurrence of a particulartransaction with a merchant (e.g., tendering or completion of a paymentfor goods and/or service); such a transaction may be, for example,payment for a meal at a restaurant visit, where the customer is able toleave a tip after he/she has left the restaurant. The tipping featureenables any tip selected or added by the customer to be directlytransmitted to the payment system, without any human interference. Forexample, after the customer has tendered his credit card to the merchantto pay for a meal, the interactive digital receipt is generated on thecustomer's mobile device. Using the mobile device, the customer can thenproceed to add a tip by selecting a tip amount from amongst recommendedoptions as per dynamic tip generator, and such tip (e.g., credit cardauthorization of the tip) is directly sent to the payment system to beadded together with the already authorized payment amount, without themerchant having to physically enter and submit the tip authorization tothe payment system.

The tipping feature 110 may be embodied in the interactive digitalreceipt in a variety of ways, as illustrated in FIG. 1D. In one example,the interactive digital receipt is a text message 120. In such example,upon receiving the receipt via text, a customer can select or add atipping amount to the transaction by replying to the text message 120and entering a number (e.g., “2.15” for a $2.15 tip), for example a tipsuggested in the message by the dynamic tip generator 172. In anotherexample, the interactive digital receipt is displayed as part of acustomer interface associated with a mobile application (“App”). In suchexample, the tipping feature 110 is a text box 122A within theinteractive receipt (e.g., interactive receipt 104), and the customercan select a tip from one of the suggested tips from the dynamic tipgenerator 172. The dynamic tip generator 172 generates the tiprecommendations based on an analysis of dynamically changing tippingprofiles based on tipping behaviors associated with tip determinants,such as the merchant, customer, location of the store, items in theshopping cart, the amount of money on the payment object being used topay for the payment transaction, and the like. The tip determinants maybe weighted, which means some determinants may be more instrumental indetermination of tip profiles than others. Further the tipping behaviormay be based on the preferences or conditions assigned by the tipdeterminants or tipping data collected over past interactions at variousmerchant locations. In another example, the customer can add on atipping amount by entering a number directly in the text box, forexample substantially similar to the tipping amount suggested by thetipping feature 110. The tipping feature 110 embodied within the App mayalso be a customer interface component 122B with default tip amountsdisplayed to the customer. The default amounts can be configured tochange based on a condition or weight specified by the merchant or thecustomer. For example, the customer may specify that the recommendationsbe generated only for a particular merchant, e.g., a salon. The paymentamount associated with the transaction (e.g., an amount equivalent to apattern of tip selections or past additions, such as 1.5%, 15.5%, etc.).The customer can quickly add the tipping amount by clicking on any ofthe default amounts displayed. In yet another example, the interactivedigital receipt is a Uniform Resource Locator (URL) link 124, whichtakes the customer to a web page to allow adding of the tipping amount.The link 124 can be a part of the text message 120, a part of the textbox 122A, the component 122B, or an electronic mail (e-mail).

The tipping feature 110 is configurable in various ways to implementvarious functionalities. In one embodiment, the tipping feature isconfigured to be available at any time, and for an unlimited timeperiod, starting after a time instance when payment has been authorized(e.g., after the customer has authorized the payment amount usinghis/her credit card to pay the merchant). In one embodiment, the tippingfeature 110 is configured to be available only for a limited, predefinedtime period, or timeframe, after the authorization for the paymentamount has been granted by the customer. As used herein, the term“timeframe” refers to a time limit during which the tipping featureremains available for receiving a gratuity amount authorization from thecustomer. The timeframe may be, for example, an hour, a day, a week, orany other desired time period (e.g., unlimited). In some embodiments,the timeframe is configured by the merchant. In other embodiments, thetimeframe is configured by an operator of the payment processing system.

The timeframe of the tipping feature 110 is initialized, or started, ata time instance at which the transaction between the customer andmerchant has occurred (i.e., a tender of payment has been completed).The timeframe decreases incrementally, from this time instance, at arate that corresponds to an ordinary passage of time. For example, oncea customer submits a payment (e.g., authorizes payment amount via adebit card), an interactive digital receipt is generated for thecustomer and the timeframe for tipping associated with that receipt isinitialized (i.e., the countdown starts) at the moment the receipt isgenerated. At the expiration of the timeframe (i.e., the countdownreaches 0), the tipping feature becomes unavailable to the customer(e.g., the feature becomes an invalidated feature). In a real-worldsetting, such time limitation helps the merchant manage its financialtransactions more efficiently. For example, a merchant often processesits financial transactions in batches and would not want to keep anyparticular transaction open indefinitely.

In one embodiment, the timeframe of the tipping feature 110 may beconfigured to incorporate a customer definition of a default gratuityamount. In particular, a customer of the customer device 100, such as acustomer, may define a nominal gratuity amount to be automatically paidto certain merchants if no gratuity amount is submitted at theexpiration of the timeframe. The nominal gratuity amount may be thebased on the past gratuity amount entered by the customer or the lowestof the tip recommendations. For example, a customer defines the gratuityamount to be $10 for the customer's favorite restaurant. In suchexample, the $10 tip is automatically authorized for any transactionwith that restaurant whenever no gratuity amount is added at thetimeframe expiration. The customer can also define the nominal gratuityamount to be zero. In some embodiments, the default gratuity amount maybe defined by the merchant. For example, a restaurant merchant may wantto configure a nominal gratuity amount to be defined for restaurantservices to groups of six parties or more. In such example, when no tipis added to the payment amount at the end of a timeframe (e.g., 2hours), an automatic 22.5% of the payment amount is authorized on thecustomer's payment card as the tip amount, and the 22.5% tip amount getsadded in the final transaction payment. The nominal amount may be basedon merchant's or customer's tip behavior. In another implementation.

Referring to FIG. 1E, the interactive digital receipt 104 can includetwo transaction components 106A, 106B, in addition to the tippingfeature 110. The transaction component 106A includes an overview of thetransaction completed between the customer and the merchant, such as thetotal amount of the transaction, the payment card used for thetransaction (e.g., last four digits of a credit card), the date, or thelike. The transaction component 106B includes the details of thetransaction, such as the name of the items purchased, the quantity, theprice, or the like. In some implementations, each item may have aseparate tip percentage associated with it so that the customer candecide if they want to tip on certain items or not. Further, some itemsmay carry a higher tip than others. In this illustration, this is shownwith stars against an item. Since iced team is starred, only iced teagets tipped. Again, the tip amount is determined based on thedynamically changing tipping behavior associated with tip determinants.

FIGS. 1F-1H illustrate a third embodiment of an interactive digitalreceipt technique implemented on a customer device 100. As illustratedin FIG. 1F, the interactive digital receipt 104 can include anengagement, or interactive, component that contains a feedback feature112. The feedback feature 112 allows the customer (i.e., payer,consumer, or the like) to submit feedback after the completion of aparticular transaction with a merchant (i.e., payee). The feedback mayinclude conditions or weight to the tip determinants to be set in thepayment processing system 164 to apply in all subsequent paymenttransactions. The feedback may also include submitting, for example, arating (e.g., 5 stars), a review, a suggestion, or the like, on variousaspects of the transaction (e.g., store cleanliness, service, products,overall visit satisfaction, reason for selective tipping, etc.). In someembodiments, the feedback is submitted directly to the merchant. In someembodiments, the payment processing system coordinates, communicates,and links with third party services associated with the merchant inimplementing the feedback feature 112. In such embodiments, the feedbackis transmitted to the third party services upon submission via theinteractive digital receipt. The third party services aggregate thefeedback in association with other feedback provided by the merchant.Such third party services may include, for example, Yelp.com, UrbanSpoon, YP.com, and the like. In an illustrative example, the feedbackfeature 112 provides an option for the customer to submit a feedback orcondition such as “do not generate tip on drink items in 112-1,” “setthe default tip based on past tip value in 112-2,” “remember the tipselection for future transactions in 112-3.” In another illustrativeexample, the feedback feature 112 provides an option for the customer tosubmit indirectly a write-up review to Yelp.com by using the feedbackfeature 112. In such example, the customer can write the review in atext box within the interactive receipt and the review is transmitted toYelp® when the customer clicks Submit.

In one embodiment, the feedback feature 112 is configurable to beavailable only for a predefined time period, or timeframe. In someembodiments, the timeframe associated with the feedback feature 112(“feedback timeframe”) is configured to be the same as the timeframeassociated with tipping feature 110 (“tipping timeframe”). For example,the timeframe may be set at one hour and at the expiration of the hour,both the tipping feature and the feedback feature are made unavailableto the customer. In some embodiments, the feedback timeframe isconfigured to be different from the tipping timeframe. For example, thefeedback timeframe may be set at one week while the tipping timeframemay be set at one hour. In such example, at the expiration of thetipping timeframe, a customer may still be able to submit feedback forthe corresponding transaction.

In some embodiments, the feedback timeframe is configured by an operatorof the payment processing system. For example, the feedback timeframecan be configured to be the same for all participating merchants of thepayment processing system. In other embodiments, the feedback timeframeis configured by a particular merchant. For example, the merchant canconfigure the feedback timeframe to be one day, one week, or any desiredamount.

In one embodiment, a particular merchant may configure the feedbacktimeframe to be tied to an incentive (i.e., “feedback reward”) forencouraging submission of a feedback. The incentive may be based on atime of submission of the feedback. For example, the customer isrewarded a “20% Off Coupon” incentive, or feedback reward, if such acondition is set. In some ways, the dynamic tipping behavior iscrowd-sourced through the feedback feature thus incentivizing thefeedbacks leads to setting of more conditions which is helpful insetting tip amounts in subsequent transactions. In another example, ifthe feedback is submitted within 10 minutes after the completion of thepayment transaction between the customer and the merchant, the reward isa 20% Off coupon; on the other hand, if the feedback is submitted within12 hours, but not exceeding the transaction timeframe allowed for thefeedback (e.g., 24 hours), the reward is a 5% coupon. In some examples,the customer may apply a gift card or a pre-paid card towards thepayment transaction. In such cases, the tip amount may be based onwhatever amount is left on the gift card and this overrides any dynamictipping based on other tip determinants.

The feedback feature 112 may be provided in the interactive digitalreceipt 104 in various configurations, as illustrated in FIGS. 1F-1G.Referring to FIG. 1G, the feedback feature 112 can be provided alongwith contents from the transaction component 106 and another engagement108. Referring to FIG. 1H, the feedback feature 112 can be providedalong with the tipping feature 110. The features 110, 112 may beconfigured according to a particular merchant's needs. For example, amerchant in the business of selling household supplies can configure theinteractive digital receipt to generate the feedback feature 112 withoutgenerating the tipping feature 110. In another example, a merchant inthe business of operating a restaurant can choose to have both thetipping feature 110 and the feedback feature 112 be generated in theinteractive digital receipt 104. One of ordinary skill in the art willappreciate that other configurations are possible.

FIG. 1I illustrate a fourth embodiment of an interactive digital receipttechnique implemented on a customer device. As illustrated in FIG. 1I,the interactive digital receipt 104 includes an engagement, orinteractive, component for generating a promotional reward feature 114.The promotional reward feature 114 allows a particular merchant toengage and incentivize a customer to interact with the merchant within apredefined time period, or timeframe. In some embodiments, the timeframeassociated with the promotional reward feature 114 (“promotiontimeframe”) is configured to be the same as the timeframe associatedwith the feedback feature 112 (“feedback timeframe”), or the timeframeassociated with the tipping feature 110 (“tipping timeframe”), or both.For example, the timeframe may be set at one hour, and at the expirationof the hour, the promotional reward feature, the feedback feature, andthe tipping feature are all made unavailable to the customer. In someembodiments, the promotion timeframe is configured to be different fromeach of the feedback timeframe and the tipping timeframe.

The time-based promotional feature 114 offers the customer a particularpromotional reward (or “promotion”) associated with the merchant and/orthe transaction completed, where the promotional reward reduces, ordecreases in value, corresponding to a decrease in the passage of timeassociated with the timeframe. For example, a $10 coupon is generatedvia the interactive digital receipt the moment a restaurant paymenttransaction occurs (e.g., authorization of payment amount is completed)and a specific threshold tip is submitted. For example, if the customersubmits a tip of 15% or higher, the coupon is generated. Any lower andthe customer does not qualify for the coupon. The coupon promotes therestaurant by offering the customer $10 off on a next meal at therestaurant. Such $10 coupon decreases in value from the moment thecoupon is generated; ultimately, the coupon decreases to a $0 valueunless the customer redeems the coupon (e.g., by buying another meal atthe restaurant). As such, the sooner the customer redeems the time-basedcoupon, the higher the value he/she gets to redeem.

The merchant may configure the rate of the reduction in value and/or thetimeframe associated with the promotional reward. In one example, therestaurant sets the $10 coupon to expire after a week, with no reductionin value at all as long as the coupon is redeemed at the end of theweek. In another example, the restaurant sets the $10 coupon to expireafter 3 days, where the value reduces each day until the value reaches$0 at the end of the third day. The value may reduce in accordance withthe passage of time or it may reduce according to a rate set by themerchant. For example, the value decreases at an exponential rate.

In some embodiments, the customer may redeem the time-based promotionalreward by completing various redemption, or promotional, activities.Some redemption activities include simply revisiting the merchant tomake another purchase for goods and/or services, as discussed in theexample above. Other redemption activities include participating in agame via the customer device. Some redemption activities includeparticipating in activities with other merchants affiliated with themerchant that offers the promotional reward. For example, the originalmerchant may offer a 15% Off Coupon, yet that coupon is redeemable onlyat the original merchant's affiliated store. The redemption activity andthe decreasing rate of the time-based reward may be configured by themerchant offering the reward. Such configurations are beneficial as theyallow the merchant to customize the promotions according to themerchant's business, such as tailoring to an advertising campaign or atargeted customer demographic.

In some implementations, the customer may apply the coupon in subsequentpayment transactions. As shown, the customer may apply a previouslygenerated coupon to a current transaction but the tip generation may bebased on the actual amount and not on the amount obtained after applyingthe coupon. In some implementations, the tip may be set to higher valuesbecause a coupon was applied.

The promotional feature 114 may be provided in the interactive digitalreceipt 104 in various configurations. As illustrated in FIG. 1I, thepromotional feature may be combined with the tipping feature 110 and thefeedback feature 112. One of ordinary skill in the art will appreciatethat other configurations are possible.

Other engagements, or interactive components, not shown in FIGS. 1B-1Imay also be implemented via the interactive digital receipt displayed onthe customer device. In one embodiment, the engagement includes aninteractive transaction record. The interactive transaction recordincludes one or more interactive digital receipts that has resulted fromone or more financial transactions belonging to the customer. Aparticular interactive record may be configured to include onlyinteractive digital receipts associated with a particular merchant. Aparticular interactive record may be configured to include allinteractive digital receipts associated with the customer, includingreceipts associated with different merchants with whom the customer hastransacted. The interactive transaction record allows the customer toorganize his/her interactive digital receipts and provides acomprehensive view of all payment transactions.

In one embodiment, the engagement includes an interactive advertisementcomponent (e.g., promotion for product and/or service) to catch thecustomer's attention using advertisement with various content. Suchadvertisement may include, for example, the promotional reward feature114 to entice the customer to “click-on” or select a particular offeringbeing displayed on the display screen. In yet another example, theadvertisement may be a plain display with no interaction required fromthe customer, where the interaction comes from the advertisement contentchanging to attract the customer's attention. The advertisement contentmay be related to the completed transaction for which the receipt 104 isgenerated. For example, for a coffee purchase transaction, theadvertisement includes information about a sustainable coffee allianceorganization. The advertisement can also include information aboutnearby merchants associated with the venue where the completedtransaction has taken place. In some embodiments, the interactiveadvertisement component is coupled to the interactive transactionrecord, where advertisement content is changed based on detailsextracted from the interactive transaction record. The advertisement orcontent information allows customer to make more informed choices withregards to tipping. For example, knowing the number of steps andindividuals involved in bringing dinner items from farm to table canencourage the customer to tip higher. Other customer engagements (orinteractive components) not discussed above, but consistent with thetechniques discussed throughout, may also be envisioned by one ofordinary skill in the art.

The order of interactive components shown in FIGS. 1B-1I can be adjustedas per customer or merchant preferences. For example, the merchant canopt to show the tip amounts before the cart value is presented or beforethe feedback option is provided. Further, the adaptive tip generationoption can be turned on or off in a setting menu.

FIG. 2 illustrates a flow diagram of a process 200 for implementing aninteractive digital receipt technique on a customer device. The customerdevice may be the customer device 100 of FIGS. 1A-1I. In someembodiments, the process 200 is implemented by the customer device. Insome embodiments, the process 200 is implemented by a payment processingsystem, such as the system 164 of FIG. 1A, or even the POS terminal. Aninstance of the payment processing system may be implemented as a mobileapplication on the customer device, such as a smartphone.

At step 202, the PPS receives a signal indicating that a financialtransaction, such as a payment transaction, between a customer of thecustomer device (e.g., a customer, a payer, a buyer, etc.) and amerchant (e.g., a seller, etc.) associated with the POS terminal. Thesignal may be communicated, or transmitted, from the merchant's POSterminal to indicate that the customer has made a payment to themerchant (i.e., to indicate that the transaction has been completed) andsent to a PPS.

At step 204, the PPS extracts information identifying tip determinantsbased on the signal or the data read off of the payment object. Forexample, the PPS determines identity of the merchant, customer, theitems forming the payment transaction, the type of items, the paymentcard, the day of transaction, and the location of the merchant's store,and the like based on the transaction data. The PPS can also extract anytransaction fingerprints associated with such tip determinants, forexample any historical tip data corresponding to the tips received bythe merchant, provided by the customer, associated with the paymentcard, etc.

At step 206, the PPS determines a dynamic tipping profile correspondingto the tip determinants identified at step 204. In some implementations,tip determinants may have a hierarchy and accordingly weights may beassociated, based on which the tipping profile is evaluated based on thetransaction fingerprints. The tip behaviors or tipping history can havepatterns which also generate a tipping profile. The tipping profile canbe a mathematical relationship or value of range of dynamic tip values.

At step 208, the PPS generates a tip amount, which is different from atip amount based solely on the payment amount corresponding to theitems. The tip amount is now configured dynamically based on the varyingbehaviors of the entities involved in the transaction.

At step 210, the PPS generates an interactive digital receipt to providean electronic record of the transaction that has been completed betweenthe customer and the merchant. The interactive digital receipt may bethe receipt 104 of FIGS. 1A-1I and may be displayed on the customerdevice. The interactive digital receipt is configured to be a “living”digital receipt that continues to be maintained and updated on the PPSand/or the customer device. The receipt allows the customer to engage inone or more engagements, or interactions, associated with thetransaction, even after the transaction has been completed (i.e.,payment has been tendered). The one or more engagements provided on thereceipt are time-based and may be configured by the merchant, thecustomer, or a combination thereof, as discussed above in thedescriptions of FIGS. 1A-1I.

At step 212, the customer device initializes a transaction timeframe tocount down in response to the interactive digital receipt beinggenerated; that is, the transaction timeframe starts decreasingincrementally until it reaches a null value once the receipt isgenerated. At step 214, the customer device displays the interactivedigital receipt on a display screen of the customer device. Theinteractive digital receipt includes one or more engagements beingdisplayed to the customer on the display screen.

In one embodiment, the engagements includes a gratuity option thatallows the customer the capability to authorize a gratuity amount (or“tip”) after the payment amount has been tendered, such as a credit cardauthorization of the payment amount (i.e., at step 202). The gratuityoption allows any adaptive or dynamic tip selected by the customer to bedirectly transmitted to the payment system. For example, once arestaurant patron has given the waiter her credit card to pay for themeal, the patron can add the tip amount by herself without needing thewaiter to physically enter the additional tip amount into the paymentsystem. In such example, the patron can simply add the tip on top of theoriginal meal amount via the interactive digital receipt, and theadditional credit card authorization is directly sent to the paymentsystem; with the gratuity option available, the patron may choose to addthe tip while she is still present at the restaurant or after she hasleft the restaurant.

As discussed above, in one embodiment, the gratuity option is availableto the customer for an indefinite time. In another embodiment, thegratuity option is limited by the transaction timeframe. In suchembodiment, the customer must utilize the gratuity option within thetransaction timeframe, i.e., before the timeframe reaches the nullvalue. When the timeframe reaches the null value, the gratuity option isdisabled and the customer is no longer able to authorize an additionaltransaction amount for gratuity. The timeframe may be configured to bean unlimited time period (i.e., no expiration).

As discussed above in FIGS. 1A-1I, the gratuity option may be provided,or displayed, via the interactive receipt along with other engagements,or interactive components, such as a time-based feedback option, atime-based promotional reward, and/or a rewards record. Accordingly, asdiscussed above, the transaction timeframe associated with theengagement(s) provided via the receipt may include one or more differenttimeframes for each type of engagement being displayed on theinteractive digital receipt (e.g., tipping timeframe, promotiontimeframe, feedback timeframe, etc.).

At step 216, the customer device determines whether the transactiontimeframe has reached a null value, i.e., “0” time left. If time stillremains, then the device continues to display the engagements to engagethe user, as indicated in step 208 If no time remains, the customerdevice processes the transaction, as indicated in step 212. Processingthe transaction may include updating the interactive digital receiptbased on the user's interactions with the one or more engagementsdisplayed on the display screen.

In one embodiment, processing the transaction at step 218 may includetransmitting to the remote system (e.g., payment processing system) anadditional payment authorization for a gratuity amount (or “tip”)submitted by the user. In one example, the customer may have chosen tointeract with the gratuity option displayed at step 214 to select thedynamic gratuity amount to the transaction. In another example, thecustomer may have predefined a nominal gratuity amount to beautomatically authorized when no gratuity amount is added for atransaction with the merchant. However, if the customer does not chooseto interact with the gratuity option and/or to define a nominal gratuityamount, no additional payment authorization step is carried out in step218.

In one embodiment, processing the transaction at step 218 may includeupdating the merchant's database with feedback completed by the customervia the interactive digital receipt. The feedback may be a condition toassign tips for subsequent payment transactions at a merchant locationor for a particular item type or payment object. The processing may alsoinclude transmitting to the customer an incentive reward for completing(i.e., submitting) the feedback. As discussed above, the incentivereward may be based on a time of submission of the feedback.

In one embodiment, processing the transaction at step 218 may includeprocessing for the customer (e.g., customer) a time-based reward forcompleting a redemption activity associated with the merchant (e.g.,merchant). The time-based reward may be maintained and accessed via theinteractive digital receipt, where the customer may choose to use thereward at any time after the redemption activity has been completed.

In one embodiment, processing the transaction at step 218 may includeupdating one or more records associated with the customer. Updating therecords may include updating the user's tip record and updating thecustomer's interactive transaction record. The interactive transactionrecord includes one or more interactive digital receipts resulting fromone or more financial transactions belonging to the customer. Aparticular interactive record may be configured to include onlyinteractive digital receipts associated with a particular merchant. Aparticular interactive record may be configured to include allinteractive digital receipts associated with the user, includingreceipts associated with different merchants with whom the customer hastransacted.

Updating the customer's tip record may include analyzing details of thetransaction between the customer and the merchant (i.e., the completedtransaction of step 202). Analysis of such details allows the PPS toautomatically create or update tipping profiles for subsequenttransactions. For example, if the customer tips more than 50% for aparticular server at a merchant location, the tipping behavior can beset to such values for subsequent transactions.

Updating the customer's interactive transaction record may includeadding the interactive digital receipt associated with the completedtransaction to a list of existing interactive digital receipts. Theinteractive transaction record may be stored on the customer device ormerchant device, such as POS terminal or a central server like PPS

FIG. 3 illustrates a screenshot of a tip dashboard 300 for determiningan adaptive value of tip for interactive digital receipts. The tipdashboard 300 may be embodied as the interactive transaction recorddiscussed above. The tip dashboard 300 may be implemented on a userinterface of a POS terminal or a customer device (e.g. customer device100 of FIGS. 1A-10 to allow a merchant or customer (e.g., a payer, abuyer, etc.) to view a list of interactive digital receipts and thedistribution of tips over a period of week, year. The interactivedigital receipts are associated with one or more completed financialtransactions between the user and one or more merchants.

Referring to FIG. 3 , the tip dashboard 300 can be implemented as adata-structure in the payment processing system. The data structureincludes a search feature 302 and a selection feature 304. Theinteractive digital receipts may be viewed and/or organized by using theselection feature 302 to select an organization based on a time, amerchant, an item type, or a transaction amount. The payment processingsystem accesses the tip amount submitted by various users at variouslocations for a variety of items on a particular day, for example usingthe search feature 304. By retrieving the information and studyingpatterns, the payment processing system can create unique relationshipsbetween a merchant, customer, item type, location and a tip amount. Forexample, by accessing the tipping behavior of John, the paymentprocessing system determines that John is more likely to tip higher atCorner Café than Bean shop. Accordingly, the payment processing systemadapts the tip amount at both the locations to reflect such a behavior.In one implementation, the pattern recognition component 174 detectspatterns in the behaviors which can be used to generate tippingprofiles.

FIG. 4 illustrates a screenshot of a gratuity (“tip”) generationdashboard 400 for generating gratuity profiles in response to aparticular transaction. The gratuity generation dashboard 400 may bepart of a user interface implemented on a merchant computing system,such as the POS terminal 154 of FIG. 1A. The gratuity generationdashboard 400 is connected to PPS that is configured to generate one ormore interactive digital receipts on a user device of a customer.

The gratuity generation dashboard 400 enables the PPS to generate atipping profile in response to a payment transaction by analyzingtipping behavior corresponding to merchants, customers, location ofmerchants, payment object provided for the payment transaction, the typeof items in the shopping card, etc. Using the gratuity generationdashboard 400, the PPS may dynamically change the tip amount that isgenerated, or displayed, to a particular customer at the completion ofevery transaction. Further, the merchant may choose between differenttemplates of a particular engagement type to be displayed. Such dynamiccapability enables the merchant to utilize the interactive digitalreceipt according to the business needs of the merchant. For example,for a frequent customer, the merchant may choose to generate a lower tipvalue or an item-based tip to reward loyalty, which is customarily notoffered as the default engagement to customers.

As shown, each of the tip determinants, such as merchant A, or customerB, is associated with a tipping profile based on its transactionfingerprint, that is past interactions with PPS. By correlating thesedata structures, the PPS can generate a dynamic or adaptive gratuityamount best suited for the specific payment transaction. Somedata-structures may include conditions which dictate whether or not tocorrelate certain data-structures or the manner in which they should becorrelated. Accordingly, a dynamic gratuity amount or range of amountsis generated as shown in 402.

FIGS. 5A-5B collectively illustrate a sequence diagram 500 illustratingan example open ticket transaction including authorization of dynamictip selection operations executed by a PPS and a POS terminal in apoint-of-sale (POS) context. The process of FIGS. 5A-5B is discussed inthe context of the scenario of FIG. 1 , s specifically offlinescenarios. However, this is merely to aid in comprehension and theprocess may be utilized in many other contexts. The solid network linesindicate connection of the mobile device with the PPS, while dotted orshaded network lines indicate that the mobile device is offline withrespect to the PPS.

At 502, the merchant inputs a request to create an open ticket for thecustomers. For example, the merchant may tap the “open ticket” buttondisplayed by the user interface (UI) to instruct the merchant device andthe payment processing system to create an open ticket. Subsequent toreceiving the instruction, the POS component of the computing devicesmay create a data record (e.g. stored in the database) to maintaininformation regarding the open ticket.

At 504, the POS component of the PPS presents a UI requesting themerchant enter a payment object for the open ticket. The merchant swipesthe first payment object, a first credit card, to provide payment objectinformation for the first credit card. In the illustrated example, uponcreating the open ticket, payment information is requested by the POScomponent prior to the merchant entering items requested by thecustomers. However, implementations are not so limited. In someimplementations, the merchant may enter items requested by the customersand request payment information from the customers at the merchant'sdiscretion or in some other point in the transaction.

At 506, after the payment object information for the first credit cardis received, the POS component may determine an initial authorizationvalue for the first credit card. In the illustrated example, the initialauthorization value for the first credit card is determined to be $200.The determination of the authorization value may be based on one or morefactors such as prior interactions with the customer, information aboutthe payment object, and so on. Once the authorization value isdetermined, the POS component displays an open ticket customer interface(UI). In the illustrated example of FIGS. 5A and 5B, the open ticket UIincludes a listing of the items. The merchant inputs one or more firstitem(s) requested by the customers from the merchant into the POSdevice. The POS component determines the cost of the first items todetermine a total value. In the illustrated example, the merchant inputstwo items, item 1 with the cost of $35 and item 2 with the cost of $60,for a total of $95. At this point in the process, the POS componentextracts relevant tip determinants off of the information obtained sofar. For example, the type of the payment object, the authorizationvalue on the payment object, identity of the customer, the merchant, theitem type, category of items, etc., are retrieved.

At 508, the dynamic tip generator computes a dynamic tip amountcorresponding to the tip determinants. For example, the dynamic tipgenerator determines a tipping profile or a plurality of profilescorresponding to the various tip determinants. Note that the dynamic tipamount is based on the cart value and other parameters which are subjectto change in an open ticket scenario. The tipping profile can be amathematical equation or a fixed percentage of tip specific for thatpayment transaction. In some cases, there can be an offline tippingprofile specifically for offline scenarios. For example, the merchantmay request higher tips to allow customer to avail open tickets. Theprocess then continues to FIG. 5B.

At 510, the merchant inputs one or more second items to the POS deviceand the POS component determines an updated total value. In theillustrated example, the merchant inputs two additional items, item 3with the cost of $50, item 2 with a cost of $65, for an updated totalvalue of $210.

At 512, the mobile device, through a local merchant application,determines an updated value of the tip or a new tip only applicable onthe newly added items. The merchant application does so based on thetipping profile at step 508. This is particularly helpful in cases wherethe mobile device is going in and out of communication network with thePPS. For example, in cases of couriers where the open ticket may closeonly after the items are delivered to the customer at their home. But atthat time the customer may add a few items to the order. If the mobiledevice is online with respect to the PPS, the tipping profile can be themost recent as accessible from the PPS. However, if the mobile device isoffline with respect to the PPS, the tipping profile can be the lastknown state. The new amount is deducted from the credit card on record.If the credit card is not authorized for the new total, the customer canbe asked to provide a second payment object. In some cases, the merchantand customer may have a bill splitting arrangement.

At 514, the merchant closes the ticket. In offline mode, this can bedone only after the mobile device comes online. At 516, the merchantindicates that the transaction has been finalized as per adaptivetipping.

The sequence of operations described above is only an example providedfor discussion purposes. Numerous other variations are possible.

FIGS. 6A and 6B are flow diagrams illustrating an example process 600for generating gratuity amounts in offline scenarios using an exemplaryopen ticket implementation, according to an implementation of thepresent subject matter. The following actions described with respect toFIG. 1-5 and may be performed by the entities of FIG. 1A.

At 602, the POS component receives a request to create an open ticketfor the customers and processes the request to create the open ticket.For example, the POS component may create a data record for the openticket transaction in the database.

At 604, the POS component provides the POS component of the merchantdevice with the current state of the open ticket and the POS componentupdates the UI of the merchant device. The user interface may vary fromimplementation to implementation and may be similar to that shown inFIGS. 5A and 5B or FIGS. 1B-1I. For example, once a payment objectand/or items have been added to the open ticket transaction, the POScomponent may update the UI to display a tipping feature similar to thatshown in FIGS. 5A and 5B.

At 606, the POS component receives an input from the merchant to performa change to the open ticket transaction. For example, the merchant mayenter item information and the cost of each item. The customer may alsoprovide his or her payment object at this time along with a limit to howmuch the merchant is authorized to charge in one open ticket.

At 608, the type of input is determined. In the example process 600, thepayment module determines if the input is the addition of a paymentobject, an addition of one or more items to the open ticket, anallocation adjustment of any bill splitting arrangement and/or anindication that the open ticket transaction is complete and should beexecuted. If the input is the addition of a payment object or additionof one or more items to the open ticket, the process proceeds to 612 onFIG. 6B. If the input is an allocation adjustment of any bill splittingarrangement, the process includes checking the authorization limit ofthe payment object and if it is not enough to cover the cost of items,the customer is asked to enter another payment object. This is not shownin the figures. If the input is an indication that the open tickettransaction is complete, the process proceeds to 610.

Turning to FIG. 6B, at 612, the tip determinants are extracted on thebasis of the payment object or one or more items added to the openticket transaction. For example, identity of the merchant, customer,item types, and payment object information is obtained.

At 614, the dynamic tip generator determines an updated total by firstcomputing a dynamic tip amount based at least on the tip determinants asdescribed in FIGS. 1-5 . The ip determinants may be weighted, that issome parameters may be more critical than others. In case the paymentobject is not authorized for the total amount, bill splitting may beinstituted. For this, using the updated total and the specificallocations, the POS component determines the non-specific remainder ofthe total to be split between the non-specific allocation instruments.Since, this is open ticket, the customer can enter more items until theopen ticket is open. In one example, the customer can enter additionalitems at 616.

At 618, if the device on which the receipt is being displayed is online,a new tip amount can be calculated by following step 614. However, ifthe device is offline, the device may access the last known value of thetip amount and the tipping profile used for the evaluation of the tipamount at step 620. Accordingly, a new tip amount is generated based onthe tipping profile at step 622. If no new items are added, the merchantcan choose to the close the ticket by following step 610 as before.

At 610, the merchant receives an indication that the open tickettransaction is complete, the PPS attempts to execute the transaction.For example, the open ticket is completed when the customer device orany other device displaying the interactive receipt comes back online.For example, the payment processing system may interact with the cardpayment network(s), bank computing device(s), payment processingsystem(s), and so on associated with the payment objects to execute thetransaction including the tip amount. More particularly, someimplementations may allow the merchant to obtain a signature from thecustomers associated with the payment objects to be processed, performany additional authorization operations needed with the card paymentnetwork for the final allocated amounts, and print receipt(s) for thecustomers. The signature/authorization/receipt process may be performedserially (e.g. obtain one signature, authorize the associated paymentobject and print receipt and repeat for each additional instrument) orin parallel (e.g. obtain a plurality of signatures, authorize theassociated payment object(s) for the final allocated amounts and printreceipts).

The process 600 described above is only an example provided fordiscussion purposes. For example, the determinations at 608 and 618 aremerely examples and other or additional determinations or options may beincluded in other implementations. In a particular example variation,additional types of payment objects may be added to the determination at618 and similar handling may be provided for the additional types ofpayment objects.

In another example variation, some implementations may provide for theoption to exit from the bill splitting operation temporarily to executethe payment transaction for one or more of the payment objects beforereturning to the bill splitting operation for the remaining paymentobjects. For example, some implementations may allow the merchant toobtain a signature from the customer associated with the payment objectto be processed, perform an authorization operation with the cardpayment network, and print a receipt for the customer before returningto the bill splitting operation for the remaining payment objects.

FIG. 7 is a block diagram illustrating embodiments of a PPS 700configured to allow processing of payment transactions between entities,such as a merchant and a buyer, or a sender and recipient of funds byauthorizing transactions initiated by registered devices. In oneembodiment, the PPS 700 may serve to aggregate, process, store, search,serve, identify, instruct, generate, match, and/or facilitateinteractions with a computer through various technologies, and/or otherrelated data. The PPS 700 may be used to collect data for laterretrieval, analysis, and manipulation, which may be facilitated throughan internal or external database. For example, the PPS 700 on receivingpayment related information may complete the transaction, generatereceipt as proof of the transaction, update inventory of the productafter the transaction, and obtain data related to the buyer involved inthe transaction, such as transaction history, location data, and thelike. In some implementations, the components of the PPS 700 can also befound in a buyer device (for example, a mobile phone of a buyer), amerchant device (for example, a point-of-sale terminal for processingpayment transactions), and a payment beacon to send and receive staticor dynamic information, for example, the payment proxy, transactionsummary or receipt, either perpetually or on activation. The devices mayhave fewer or more components than defined here as will be clear bycontext.

The PPS 700 may communicate with a POS terminal (e.g., transactionprocessing software applications executing on a tablet, or a computer)and various neighboring and remote, but connected, devices, such asbuyer devices. The PPS 700 has the circuitry and logic to register a newdevice presented at the time of transaction along with a payment object,and mapping the device with the object or without the object for anysubsequent payment transactions. The device may be registered in avariety of ways based on the characteristics that are obtained. Forexample, if the radiated performance is to be used as a factor in deviceregistration and identification, the antenna transmitter and receiver ofthe PPS 700 are initialized. In another example, if the manufacturingtolerances are to be measures, components like the sensors andaccelerometers of the PPS 700 are activated.

Users 702A, who may be buyers, merchants, consumers, senders orrecipients of funds, buyers, sellers, and/or other entities or systems,may engage information technology systems (e.g., computers, mobiledevices, laptops, servers) to facilitate processing of information, suchas transactional, financial, and so on. It should be noted that the term“server” as used throughout this application refers generally to acomputer, other device, program, or combination thereof that processesand responds to the requests of remote users across a communicationsnetwork. Servers serve their information to requesting “clients” 702Bconnected to the users 702A. The term “client” or “buyer device” as usedherein refers generally to a computer, program, other device, userand/or combination thereof that is capable of processing and makingrequests and obtaining and processing any responses from servers acrossa communications network 704. Networks 704 facilitate the transfer ofinformation from source points to destinations. The users (e.g.,merchants) may directly interact with the PPS 700, e.g., via the userinputs devices 605.

In one implementation, the PPS 700 can be configured to receive apayment card or payment card information to process payment cardtransactions (i.e., those involving reading of a payment card physicallyprovided by the buyer at the merchant's location), as well ascard-not-present (CNP) transactions (i.e., those where the instrument isnot physically presented at the time that the payment is effected, e.g.,through payment proxy), either through a card reader 606 or by providinga graphical user interface 708 to accept financial account informationof the user 702A initiating the payment. A payment card transaction maybe any transaction where a merchant or a buyer uses a payment card topurchase a product or service offered by the merchant, for example, byswiping a user's credit card through a magnetic rails or chip contacts706 or by providing the information through voice, text, or other wiredor wireless data communication techniques. The term “swipe” here refersto any manner of triggering a magnetic rails or chip contacts 706 toread data from a payment card, such as by passing a card into or througha magnetic stripe card reader, optical scanner, smartcard (card with anembedded IC chip) reader (e.g., an EMV-compliant card reader or NFCenabled reader), radio frequency identification (RFID) reader, or thelike. The magnetic rails or chip contacts are integrated within the PPS700 (as shown) or connected externally with the PPS controller 700and/or client(s) 702B as peripheral devices 710. If the card reader 706is connected externally, the peripheral devices 710 may be connected viawired or wireless communication network 704 and interact to each otherthrough customized interfaces. In one implementation, the PPS 700 can beconnected to an audio plug of another device, such as the POS terminal.If the PPS 700 is integrated within the POS terminal, the one or moreinterfaces and components can be configured to accept payment datathrough various communication protocols. Accordingly, hardwareimplementation may include creation of slots, magnetic tracks, and railswith one or more sensors to facilitate a user 702A, e.g., a merchant, todetect and accept a payment card. In one implementation, the paymentcard and the peripheral devices 606 may support the same technology forshort-range (typically less than 100 meters) and/or low power wirelesscommunication protocols and technologies, such as Bluetooth Low Energy(BLE), standard Bluetooth, WiFi, Near Field Communication (NFC) orRadio-Frequency Identification (RFID). According to the communicationprotocol preferred or implemented, the PPS 700 may require additionalsteps to configure the rails or chip contacts 706 to operate and workalongside the PPS 700. For example, a pairing component (describedlater) may be used to connect, synchronize, and pair various devices tofacilitate exchange of data obtained off the payment card.

The term “payment card” or ‘payment object’ refers to a paymentmechanism that includes a conventional debit card, a conventional creditcard, a prepaid gift card, or the like, a smartcard that has an embeddedintegrated circuit chip (e.g., Europay-MasterCard-visa (EMV) card), aproxy card, or any card that functions as a combination of any of thesemechanisms. The term “proxy card” as used herein refers to a card thatmay or may not have a card number/account number that appears to be thatof a real credit or debit card account (i.e., it is in the correctformat), but where that card/account number is actually only a proxy forthe buyer's real card/account number. The card/account number generallyadheres to a naming standard set by the financial institution associatedwith or issuing the payment card. Other examples of payment card mayalso include a prepaid card, a gift card, a rewards card, a loyaltypoints card, a frequent flyer miles card, a check, cash, or any otherkind of payment instrument that holds financial value or provides apromise to pay at a later time.

The payment card used in the example above is one type of a financialinstrument. Other types of financial instruments, other than the paymentcard, can be used to initiate the transfer of funds. Another example ofa financial instrument is a biometrically identifiable instrument, suchas a person's finger (e.g., for fingerprint recognition), face, iris orretina, heartbeat, voice pattern, genetic parameter unique to the user,etc. Alternatively, a financial instrument can be a software instrumentor virtual instrument, such as a virtual wallet, optionally embedded ina hardware device to enable contact or contactless payments.

Payment Object Reader Architecture

In one implementation, the PPS 700 may be based on computer systems thatmay comprise, but are not limited to, PPS units 712 and memory 714.Furthermore, PPS units can comprise hardware and/or software components,referred to as PPS units 712, which may comprise a central processingunit (“CPU(s)” and/or “processor(s) and/or microprocessor(s)” (theseterms are used interchangeably)) 716 and an interface bus 718, which maybe interconnected and/or communicating through a system bus 720 on oneor more motherboard(s) having conductive and/or otherwise communicativepathways through which instructions (e.g., binary encoded signals) maytravel to enable communications, operations, storage, etc. The interfacebus 718 may also include other interfaces or adapters specific tonetwork, storage, peripherals, and input-output interface(s), throughwhich data may pass into and out of a computer and which allow users toaccess and operate various system components. The interface bus 718 maybe connected to external units, such as peripheral devices 710 orclient(s) 702B via communication network 704. Each of the exemplarycomponents 712 is now described in detail.

Processor(s)

The CPU 716 may incorporate various specialized processing units, suchas, but not limited to: integrated system (bus) controllers, memorymanagement control units, floating point units, and even specializedprocessing sub-units like graphics processing units, digital signalprocessing units, and/or the like. In various embodiments, the processorcore may be a low-power/ultra-low power/low-cost microcontroller;examples include an Intel Processor like Intel Atom, Apple A4, NVidiaTegra 2, Marvell Armada, Qualcomm Snapdragon, Samsung Hummingbird andExynos, Texas Instruments OMAP and MSP microcontroller, ARM Holdingsprocessor like the Cortex-A, -M -R, Series, or ARM series and/or thelike processor(s). Should processing requirements dictate a greateramount speed and/or capacity, distributed processors (e.g., DistributedPPS 700), mainframe, multi-core, parallel, and/or super-computerarchitectures may similarly be employed. Alternatively, shoulddeployment requirements dictate greater portability, smaller PersonalDigital Assistants (PDAs) may be employed.

Depending on the particular implementation, features of the PPS 700 maybe achieved by implementing a microcontroller, such as Freescale'sKinetis K21D; and/or the like. Also, to implement certain features ofthe PPS 700, some feature implementations may rely on embeddedcomponents, such as: Application-Specific Integrated Circuit (“ASIC”),Digital Signal Processing (“DSP”), Field Programmable Gate Array(“FPGA”), and/or the like embedded technology. Depending on theparticular implementation, the embedded components may include softwaresolutions, hardware solutions, and/or some combination of bothhardware/software solutions.

Interface Bus and Adapters

Interface bus(ses) 718 may accept, connect, and/or communicate to anumber of interface adapters, although not necessarily in the form ofadapter cards, such as but not limited to: input-output interfaces (I/O)722, storage interfaces 724, network interfaces 726, and/or the like.Optionally, cryptographic processor interfaces 728 may be connected tothe interface bus 718.

Storage interfaces 724 may accept, communicate, and/or connect to anumber of storage devices such as, but not limited to: storage devices730, removable disc devices, and/or the like. Storage interfaces 724 mayemploy connection protocols such as, but not limited to: (Ultra)(Serial) Advanced Technology Attachment (Packet Interface) ((Ultra)(Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE),fiber channel, Small Computer Systems Interface (SCSI), Universal SerialBus (USB), and/or the like.

Input-Output interfaces (I/O) 722 may accept, communicate, and/orconnect to user input devices 705, peripheral devices 710, such asexternally connected card readers, cryptographic processor devices 731,and/or the like. I/O may employ connection protocols such as, but notlimited to: audio: analog, digital, monaural, RCA, stereo, and/or thelike; data: Apple Desktop Bus (ADB), IEEE 1394a-b, serial, universalserial bus (USB); USB 2.0; USB 3.1; USB Type C; Ethernet; infrared;joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; videointerface: Apple Desktop Connector (ADC), BNC, coaxial, component,composite, digital, Digital Visual Interface (DVI), high-definitionmultimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or thelike; wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g.,code division multiple access (CDMA), high speed packet access(HSPA(+)), high-speed downlink packet access (HSDPA), global system formobile communications (GSM), long term evolution (LTE), WiMax, Li-Fietc.); and/or the like. In various embodiments, an audio or videodisplay with a touch screen and driver may be included, the touch screenbeing based upon a variety of later-developed or current touch screentechnology including resistive displays, capacitive displays, opticalsensor displays, electromagnetic resonance, or the like. Additionally,touch screen display may include single touch or multiple-touch sensingcapability. Any display technology may be used for the output display,such as a Liquid Crystal Display (LCD) or solid state device such aslight-emitting diode (LED) or organic light-emitting diode (OLED),Plasma display, trans-reflective (Pixel Qi) display, electronic inkdisplay (e.g. electrophoretic, electrowetting, interferometricmodulating). In various embodiments, the resolution of such displays andthe resolution of such touch sensors may be set based upon engineeringor non-engineering factors (e.g. sales, marketing). In some embodiments,speakers and LED indicators can be used to present audio and visualidentifiers of transaction and device status. In addition, buttons maybe configured to power PPS 700 on or off, operate the controller orreset the controller 600.

In some embodiments of the PPS 700, image capture device may beincluded, which may further include a sensor, driver, lens and the like.The sensor may be based upon any later-developed or convention sensortechnology, such as CMOS, CCD, or the like. Image recognition componentsmay be provided to process the image data. For example, such componentscan support functionalities including, but not limited to, barcodedetection, facial recognition, camera parameter control, etc.

Network interface(s) 726 may be regarded as a specialized form of aninput-output interface. One or more network interfaces 726 may be usedto engage with various communications network types 704. For example,multiple network interfaces may be employed to allow for thecommunication over broadcast, multicast, and/or unicast networks.Through a communications network 704, the PPS controller 700 isaccessible through remote clients 702B (e.g., computers with webbrowsers) by users 702A. Network interfaces 726 may employ connectionprotocols such as, but not limited to: direct connect, Ethernet (thick,thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring,wireless connection such as IEEE 802.11a-x, and/or the like. Shouldprocessing requirements dictate a greater amount speed and/or capacity,distributed network controllers (e.g., Distributed PPS architectures maysimilarly be employed to pool, load balance, and/or otherwise increasethe communicative bandwidth required by the PPS 700.

In some implementations, the network interfaces 726 may becommunicatively coupled to hardware components, which facilitatedetection of payment cards. For example, the network interfaces 726 maycouple to a payment card slot or rail designed to accept payment cardsthrough swipe or insertion or any other action. In another example, thenetwork interfaces 726 may couple to one or more sensors included todetect presence of payment card or a tap of the payment card onto asurface of the PPS 700.

In various embodiments, the network interface 726 may also supportwireless data transfers between the PPS 700 and external sources, suchas clients 602B and cameras, or the like. Wireless protocols may includeWi-Fi (e.g. IEEE 802.11a/b/g/n, WiMax), Bluetooth or Bluetooth lowenergy (BLE); infrared, and the like, through BLE interface, WiFiinterface, QR interface, NFC interface, EMV interface, cellulartechnology interface, and other interface(s), described subsequently.

According to one implementation, BLE interface (“BLE”) 732 is configuredto work on Bluetooth® or BLE® protocol to facilitate communication witha BLE transceiver installed on other devices. In one implementation, BLEis intended for low-power and low-latency applications for wirelessdevices within a short range, such as up to about 50 meters. BLEinterface 732 may be used in applications requiring intermittentcommunications, smaller amounts of data transfer and bandwidths, and/orlow duty cycles. BLE interface 732 can be configured to use only afraction of the power as compared to other interfaces. In many cases,BLE interface 732 may be able to operate more than a year on the powersource without charging.

BLE interface 732 is capable of being paired with a peripheral device,such as another reader, a payment card, or a client 702B associated witha user 702A, thus allowing the PPS 700 to (a) serve as a “beacon” andbroadcast data and/or (b) become a relay point between the PPS 700 andpayment card, card reader 706 or a client 702B serving as a point ofsale terminal for a merchant. The BLE interface 732 allows thecontroller 700 with BLE interface 732 can be placed at merchantlocations, museums, ski resorts, state parks, entertainment venues,parking garages, etc.

As defined herein, a beacon is a short range communication device havinga known or fixed location that provides a signal that can be detected bymobile devices within proximity of the beacon. For example, BLEinterface 732 can transmit a radio frequency (RF) signal that includesits position coordinates (e.g., latitude, longitude), which can bedetected by a mobile device. Alternatively, BLE interface 732 cantransmit other data, such as payment proxy related to the financialaccount information of the user 702B.

The PPS 700 BLE beacon allows for constant, scheduled or random scanningof other Bluetooth peripherals and devices. In one implementation, acomponent, such as BLE interface component, within the PPS 700 and/orthe client 702B can be set to run in the background under a BLEprotocol, persistently, intermittently or on activation monitoring for asignificant change in location and/or presence of an appropriate BLEperipheral or beacon at a merchant or vendor location. BLE beacon alsoallows for persistent or intermittent transmission of data. For example,BLE beacon may persistently transmit or receive information related topayment proxy associated with the client 702B or PPS 700.

When the owner or user of the client 702B or payment card enters a storehaving PPS 700 as a point of sale terminal, he or she would get in theBLE network radius of the PPS 700. PPS 700 then serves as abidirectional conduit for the card reader 706 to communicate with theCPU 724 collecting or handling the credit card transaction. Along withreceiving transaction data or any other data by the BLE interface 732,the PPS 700 may also encrypt, decrypt, or store the data for futureprocessing. It does these actions in addition to running the paymentapplication itself, which may display items for sale, up-sell based onpurchases, allow confirmation of purchases, application of coupons, theability to provide feedback, etc.

In one implementation, the PPS 700 or the client 702B may be connectedto a BLE peripheral device having BLE interface 732 functionalities. Insome implementations, the payment card may include a chip supporting BLEfunctionalities. A control logic unit (not shown) may also be includedto bridge BLE interface either to ISO 7816 contact interface or ISO14443 contactless interface to provide for autonomous bi-directionaldata transfer between paired devices. In one implementation, the PPS 700is capable of communicating using Bluetooth, and is thus able to pairwith a peripheral device 710 to obtain payment object information from aphone that at least has Bluetooth capabilities. In one implementation, aplurality of BLE peripheral devices may be connected via the BLEprotocol, or other communication network, to form a mesh network. Such amesh network may allow for transfer of data between the peripheraldevices, even those that are more than the distance prescribed by theBLE protocol.

Similar to BLE beacons, data can be exchanged using other kind of RFbeacons, infrared beacons, cellular communications (CDMA, GSM, LTE,etc.), beacons, pattern generation beacons, such as barcodes, QuickResponse (QR) codes, or a radio frequency identifier (RFID) tag. QR codeor NFC may have short range but high accuracy; Wi-Fi or Bluetooth mayhave mid-range and medium accuracy; and cellular may have long-range butlow accuracy. In some embodiments, the controller 700 can receive andpermanently store payment information so that the controller 600 acts asa payment object that does not require a payment card or other paymentobject to be present.

In one example, an NFC interface 734 (“NFC”) can allow for close rangecommunication using standards such as ISO 18092, ISO 21481, TransferJet®protocol and in compliance with FIME certifications. Close rangecommunication with the NFC interface may take place via magnetic fieldinduction, allowing an NFC interface chip 634 to communicate with otherNFC devices or to retrieve information from tags having RFID circuitryvia the NFC interface. In instances where it is desired to read an NFCenabled payment object, or an NFC enabled payment object is determinedto be in proximity to the CPU 716 may be configured to drive antenna 745via a driving circuit (not shown) to induce a magnetic field capable ofbeing modulated by the NFC enabled payment object. From here, themodulated magnetic field signal may be converted into a digital signalthat CPU 716 can interpret via the NFC component 734. On the other hand,when it is desired to transmit data via antenna 745, CPU 716 may beconfigured to disable the driving circuit and transmit data using theNFC protocol by instructing a NFC modulator (not shown) to modulate themagnetic field to which antenna 745 is operatively coupled. In someembodiments, there can be a switch within the NFC modulator to turn onor off the load applied to the antenna 745. The switch can be under thecontrol of the CPU 716. In some embodiments the antenna 745 can driftfrom a desired frequency (become detuned). This can be the result of ametal object being in the proximity of device 610 or reader 700. Themonitor circuit (not shown) can monitor the frequency of the antenna745, and determine when the frequency of the antenna 745 has driftedaway from the desired frequency. When the it is determined that the NFCantenna 745 is out of tune, NFC antenna monitor circuit can work inconcert with the CPU 716 to vary one or parameters such as capacitance,voltage, or impendence of the antenna 745 to tune the NFC antenna 745.The antenna 745 along with transmitter-receiver 644 is configured todetect characteristics, such as radiated performance, radiated signalstrength, frequencies, etc., via radio communication protocol.

In another example, an EMV interface 736 (“EMV”) can allow the PPS 700to accept Chip and PIN cards follow technical standards more formallyknown as EMV, after Europay, MasterCard and Visa (EMV). In oneimplementation, the EMV interface complies with EMV's Level 1, Level 2and Level 3 certifications. In some instances, CPU 716 receives paymentdata read by the EMV interface 736 via the card contacts (not shown), oralternatively from a magnetic stripe reader reading payment data from amagnetic stripe card. The payment data received at the CPU 716 isstored, either temporarily or permanently, in memory 714 of the reader700. The payment data stored in memory can then be transmitted via theNFC antenna 718. The network interfaces 626 may work in conjunction withcomponents explained later.

In other implementations, a plurality of beacon technologies may be usedbased on specific accuracy or power requirements. Such technologies maybe combined based on weight or some other relationship. In yet anotherimplementation, selections may be made based on user preference oravailability of the beacon technology at that time. For example, thereader 700 may be configured to provide and detect a plurality ofbeacons. For example, if a camera is on, a QR code on the client 702Bdisplay may be read, for example to pair two payment devices. If onlycellular is on, a modem may detect a femtocell may be nearby. The client702 B, such as a merchant's register or point of sale terminal, maycombine data from the multiple beacons and use such data for analysis oftransactions over a course of time. For example, the buyer device 702Bmay be configured to use Wi-Fi RSSI/RTT and BT RSSI/RTT measurementsfrom a first beacon, QR code value from a second beacon, and WiFi RSSIand cellular measurements from a third beacon for accurately identifyingand establishing secured connections with the buyer device 702B.

The beacons can be dynamic with data and other beacon parameterschanging as per environment or the type of device pairing with thereader 700; in other implementations, the beacons can be static anddisplayed using LED displays, electronic displays, or the like,described with reference to I/O interface.

In one embodiment, the PPS 700 may also be connected to and/orcommunicate with entities such as, but not limited to: one or moreusers, for example users 602A, associated with user input devices 705;one or more users 602A through their respective buyer devices 702B;peripheral devices 710; an internal or external cryptographic processordevice 731; and/or a communications network 704.

Communications Network

The network 704 can include any combination of local area and/or widearea networks, using both wired and wireless communication systems. Insome embodiments, the network 704 uses standard communicationstechnologies and/or protocols. Thus, the network 704 can include linksusing technologies such as Ethernet, 802.11, a Wi-Fi, a Bluetoothnetwork; and/or the like worldwide interoperability for microwave access(WiMAX), 3G, 4G, CDMA, digital subscriber line (DSL), etc. Similarly,the networking protocols used on the network 608 may includemultiprotocol label switching (MPLS), transmission controlprotocol/Internet protocol (TCP/IP), hypertext transport protocol(HTTP), and/or file transfer protocol (FTP). Data exchanged over thenetwork 708 can be represented using technologies and/or formatsincluding hypertext markup language (HTML) or extensible markup language(XML). In addition, all or some links can be encrypted usingconventional encryption technologies such as secure sockets layer (SSL),transport layer security (TLS), and Internet Protocol security (IPsec).Additionally, the communication network may be a mesh network. Forexample, in a wireless local area network (WLAN), network devices may beconfigured to receive and forward communications which are ultimatelydestined for a different device. These types of networks are genericallyreferred to as “mesh” networks, where network nodes may form a “mesh” ofpaths for which communications may travel to reach their destination.Wireless networks may use beacon transmissions to advertise thenetwork's existence, as well as provide information about the networkand capabilities associated with the network. Different kinds ofbeaconing mechanisms may be used, for example, one for infrastructuremode networks (also called basic service set (BSS) networks) and one forad-hoc mode networks (also called independent basic service set (IBSS)networks). In infrastructure networks, access points (APs) are theentities responsible for generating beacons whereas in ad hoc networks,all network nodes (including user stations) participate in thegeneration of beacons. The ad hoc network beacons (referred to as IBSSbeacons) are used to advertise the network (which consists of all thenodes) as a whole while the infrastructure network beacons (referred toas BSS beacons) are generated by an AP and meant to advertise theexistence of only that individual AP.

Clock

Clock 738 may have a crystal oscillator that generates a base signalthrough the reader's circuit pathways. The clock 738 may be coupled tothe system bus 720 and various clock multipliers that increase ordecrease the base operating frequency for other componentsinterconnected in the PPS 700.

Power Source

The units 712 may also include a power source 740. The power source 640may be of any form capable of powering small electronic circuit boarddevices such as the following power cells or batteries: alkaline,lithium hydride, lithium ion, lithium polymer, nickel cadmium, solarcells, and/or the like. Other types of AC or DC power sources may beused as well. The power source 740 is connected to at least one of theinterconnected subsequent components of the PPS 700 thereby providing anelectric current to all subsequent components. In one example, the powersource 740 is connected to the system bus 704. In an alternativeembodiment, an outside power source 740 is provided through a connectionacross the I/O 722 interface. For example, a USB connection can carryboth data and power across the connection and is therefore a suitablesource of power. To this end, coupled to power source 740 may be a USBmicro interface (not shown) configured to receive a USB micro jack,although other types of connectors are anticipated. In certainembodiments, connection of a jack to USB micro interface can activate aswitch within power source 740 to override power supplied by thebattery. This allows for battery power to be conserved for situationswhere external power cannot be provided. Furthermore, power source 740may also include a battery charger to allow the battery to be chargedwhen external power is supplied via USB micro interface.

In one implementation, the power source 740 may include a selector (notshown) to selectively power one or more units within the PPS 700. Forexample, the power source 740 may power the BLE network interface andBLE component and power the CPU 716 only on receiving a wake up signal,using an activation signal, triggered by a tactile, visual, or audioinput. To this end, the PPS 700 may include wake-up electronics (notshown) configured to wake-up the PPS 700 from a low-power state to anactive state in response to detection of a payment object. In someembodiments, wake-up electronics can also power down PPS 700 to alow-power state after a predetermined amount of time or after completionof a communication.

Cryptographic Processor

A cryptographic processor 642 and/or transceivers (e.g., ICs) 644 may beconnected to the system bus 620. In another embodiment, thecryptographic processor and/or transceivers may be connected as eitherinternal and/or external peripheral devices 610 via the I/O interfacebus 622. To this end, the transceivers 644 may be connected toantenna(s) 645, thereby enabling wireless transmission and reception ofvarious communication and/or sensor protocols. For example theantenna(s) may connect to a transceiver chip or a wirelessmicrocontroller targeting Bluetooth applications, e.g., providing802.11n, Bluetooth 4.2, Bluetooth 2.1+EDR, FM,GSM/EDGE/GPRS/2G/3G/HSDPA/HSUPA/LTE (4G) communications, globalpositioning system (GPS) thereby allowing PPS 700 to determine itslocation, for example. A separate GPS unit 746 (also referred to as thelocation component) may be used to determine the location of a merchantor buyer performing a payment transaction using a payment card. The GPSunit may work on any of the protocols mentioned above. The locationinformation may be used to advertise location specific information tothe user.

Furthermore, the communicative instructions may be stored and/ortransmitted in batches (e.g., batches of instructions) as programsand/or data components to facilitate desired operations.

Peripheral Devices

Peripheral devices 710 may be connected and/or communicate to I/Ointerface 722 and/or other facilities of the like such as networkinterfaces, storage interfaces, directly to the interface bus 718,system bus, the CPU, and/or the like. Peripheral devices 710 may beexternal, internal and/or part of the PPS 700. Peripheral devices 710may include: antenna, audio devices (e.g., line-in, line-out, microphoneinput, speakers, etc.), cameras (e.g., still, video, webcam, etc.),dongles (e.g., for ensuring secure transactions with a digitalsignature, and/or the like), external processors (for addedcapabilities; e.g., crypto devices 731), force-feedback devices (e.g.,vibrating motors), network interfaces, printers, scanners, storagedevices, transceivers (e.g., cellular, GPS, etc.), video devices (e.g.,goggles, monitors, etc.), video sources, visors, and/or the like.

The card reader 700 may comprise user interfaces, such as, for example,a PC/SC EMV L1/L2/NFC certified Smart Card Reader, a keypad for PINentry, such as key keypad, a display, such as the illustrated LCDdisplay, etc., and electrical interfaces, an interface for back-upbattery power, an interface for a display, a power interface, LED lightsfor indicating status of a transaction, a buzzer, etc. The card readermay be, for example, PCI v3 compliant and configured to facilitate theacceptance of credit/debit card payments.

A sensor 790 may be included. In some embodiments, the sensor 790 mayinclude accelerometers, antenna decouplers, signal generator, signalmodification and conditioning components to detect certaincharacteristics of neighboring devices. The characteristics aregenerally physical, mechanical or design related. The sensor 790 is alsocapable of sending and receiving signals or test parameters, theparameters are then compared internally to determine whether the valuescorrespond to a known device.

Peripheral devices 710 may also include sensors, devices, and subsystemscan be coupled to network interface to facilitate multiplefunctionalities. For example, motion sensor, magnetic, light sensor, andproximity sensor can be coupled to network interface to facilitateorientation, detection, lighting, and proximity functions of the PPS700, by analyzing any input, such as audio, visual, tactile, mechanical,electrical, magnetic, hydraulic, electromagnetic input, and the like.Location processor (e.g., GPS receiver similar to GPS 646) can beconnected to the network interface to provide geo-positioning. Motionsensor can include one or more accelerometers configured to determinechange of speed and direction of movement of the PPS 700. Magneticsensors may detect presence or absence of a payment card anddifferentiate a payment card from other cards.

Peripheral devices 710 may also include a camera subsystem and anoptical sensor, e.g., a charged coupled device (CCD) or a complementarymetal-oxide semiconductor (CMOS) optical sensor, can be utilized tofacilitate camera functions, such as recording photographs and videoclips.

Peripheral devices 710 may also include an audio subsystem can becoupled to a speaker and a microphone to facilitate voice-enabledfunctions, such as voice recognition, voice replication, digitalrecording, and telephony functions. Audio subsystem can be configured toreceive voice commands from the user.

Peripheral devices 710 may also include an I/O subsystem that caninclude touch surface controller and/or other input controller(s). Touchsurface controller can be coupled to a touch surface or pad. Touchsurface and touch surface controller can, for example, detect contactand movement or break thereof using any of a plurality of touchsensitivity technologies, including but not limited to capacitive,resistive, infrared, and surface acoustic wave technologies, as well asother proximity sensor arrays or other elements for determining one ormore points of contact with touch surface. Touch surface can include,for example, a touch screen.

Other input controller(s) can be coupled to other input/control devices,such as one or more buttons, rocker switches, thumb-wheel, infraredport, USB port, and/or a pointer device such as a stylus. The one ormore buttons (not shown) can include an up/down button for volumecontrol of speaker and/or microphone.

In one implementation, a pressing of the button for a first duration maydisengage a lock of the touch surface; and a pressing of the button fora second duration that is longer than the first duration may turn powerto PPS controller 100 on or off. The user may be able to customize afunctionality of one or more of the buttons. The touch surface can, forexample, also be used to implement virtual or soft buttons and/or akeyboard. The touch surface may also activate the PPS controller toactively relay information. At all other times, the reader 700 may bedormant to conserve power.

User input devices 705 often are a type of peripheral device 710 (seebelow) and may include: card readers, dongles, finger print readers,gloves, graphics tablets, joysticks, keyboards, microphones, mouse(mice), remote controls, retina readers, touch screens (e.g.,capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g.,accelerometers, ambient light, GPS, gyroscopes, proximity, etc.),styluses, and/or the like. The card readers, as mentioned before, may beconfigured to read a variety of payment cards. Such card readers mayeither be dongle like or puck style.

Cryptographic units such as, but not limited to, microcontrollers,processors 716, interfaces 718, and/or devices 731 may be attached,and/or communicate with the PPS 700. Cryptographic units support theauthentication of communications from interacting agents, as well asallowing for anonymous transactions. Cryptographic units may also beconfigured as part of the CPU.

It should be noted that although user input devices 705 and peripheraldevices 710 may be employed, the PPS 700 may be embodied as an embedded,dedicated, and/or monitor-less (i.e., headless) device(s), whereinaccess would be provided over a network interface connection.Additionally, part or all peripheral devices may be integrated withinthe PPS 700.

Memory

Memory 714 may further include, but is not limited to, one or morecomponents 748 that include programs that supplement applications orfunctions performed by the PPS 700, database 750, operating system 752,random access memory (RAM) 754, read only memory (ROM) 756, and storagedevice 730, etc., into which data may be saved that serves, amongstother things, as repository for storing data pertinent to functioning ofthe components.

The PPS 700 may employ various forms of memory 614, such as ROM 754, anda storage device 730. Storage devices may include a drum; a (fixedand/or removable) magnetic disk drive; a magneto-optical drive; anoptical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW),DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Arrayof Independent Disks (RAID)); solid state memory devices (USB memory,solid state drives (SSD), etc.); other processor-readable storagemediums; and/or other devices of the like.

PPS Components

The memory 714 may contain a collection of program and/or databasecomponents and/or data such as, but not limited to: operating systemcomponent(s) 752 (operating system); information server component(s) 758(information server); user interface component(s) 708 (user interface);Web browser component(s) 760 (Web browser); database(s) 750;cryptographic server component(s) 762 (cryptographic server); thecomponent(s) 748; and/or the like (i.e., collectively a componentcollection). These components 748 may be stored and accessed from thestorage devices and/or from storage devices accessible through aninterface bus 718.

Operating System

The operating system component 752 is an executable program componentfacilitating the operation of the PPS 700. The operating system canfacilitate access of I/O, network interfaces, peripheral devices,storage devices, and/or the like. In various embodiments, any number ofcurrent or future operating systems may be supported such as: any highlyfault tolerant, scalable, portable, ROM-able, real-time, deterministic,multitasking and secure kernels systems, e.g., μC/OS-III, μC/OS-III,Apple Macintosh OS X (Server); Unix and Unix-like system distributions;Linux distributions; limited and/or less secure operating systems, e.g.,AppleMacintoshOS, MicrosoftWindows XP, Windows Server2003, WindowsServer 2008, Windows Server2012, Windows Vista®, Windows 7, and Windows8, Blackberry OS (e.g., Blackberry 10), Firefox OS, Sailfish OS, Tizen,Ubuntu Touch OS, Chrome OS, iPhone OS (e.g. iOS), WindowsMobile (e.g.Windows 10 Mobile), Google Android (e.g. Lollipop 5.1); and/or the like.In various embodiments of the present subject matter, the operatingsystem may be a multi-threaded multi-tasking operating system.Accordingly, inputs and/or outputs from and to a display and inputs/oroutputs to physical sensors may be processed in parallel processingthreads. In other embodiments, such events or outputs may be processedserially, or the like. Inputs and outputs from other functional blocksmay also be processed in parallel or serially, in other embodiments,such as image acquisition device and physical sensors.

The operating system 752 may provide communications protocols that allowthe PPS 700 to communicate with other entities through a communicationsnetwork 713. Various communication protocols may be used by the PPS 700as a subcarrier transport mechanism for interaction, such as, but notlimited to: multicast, TCP/IP, UDP, unicast, and/or the like.

Information Server

The information server 758 may: support secure communications protocolssuch as, but not limited to, File Transfer Protocol (FTP); HyperTextTransfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS),Secure Socket Layer (SSL), messaging protocols; provide results in theform of Web pages to Web browsers; and allows for the manipulatedgeneration of the Web pages through interaction with other programcomponents.

Web Browser

A Web browser component 760 is a stored program component that isexecuted by a CPU. The Web browser may be a hypertext viewingapplication such as Google Chrome or Macintosh Safari. Web browsers andlike information access tools may be integrated into PDAs, cellulartelephones, and/or other mobile devices. Also, in place of a Web browserand information server, a combined application may be developed toperform similar operations of both. The combined application wouldsimilarly affect the obtaining and the provision of information tousers, user agents, and/or the like from the enabled nodes. The webbrowser may be coupled to a web server (not shown). In otherimplementations, the PPS 700 may host a website (hereinafter, “systemwebsite”) that includes one or more graphical user interfaces (GUIs) fororganizing and presenting content to users. For example, through thesystem website, users create account logins to connect to their socialidentities (e.g., social profiles or social accounts), read content(e.g., messages, comments, posts), create or post content, communicatein real-time with other users (e.g., chat), and/or otherwise engage orinteract with other users of the system website (e.g., “friends,”“followers,” “social contacts,” or other types of social networkconnections). In some embodiments, the user interactions on the systemwebsite lead to internal API communication, which involves the PPS 700monitoring the user interactions for an indication of an intent totransfer money, sending, in response to such indication, requests (e.g.,POST or GET requests) to the API of the server(s) to query thedatabase(s) 750, and displaying the data returned by the API of theserver(s) as appropriate. The indication of the intent is determined maybe based on an identification of a user input, e.g., a string ofcharacters, that has a particular syntax, the syntax being a monetaryindicator preceding one or more alphanumeric characters. The user inputhaving the syntax operates as a trigger to send money to a payment proxyrepresented by the user input.

User Interface

The user interface 708 may allow for the display, execution,interaction, manipulation, and/or operation of program components and/orsystem facilities through textual and/or graphical facilities throughone or more interaction interface elements, such as check boxes,cursors, menus, scrollers, and windows (collectively and commonlyreferred to as widgets) to facilitate the access, capabilities,operation, and display of data and computer hardware and operatingsystem resources, and status. Graphical user interfaces (GUIs) 708 maybe used to provide a baseline and means of accessing and displayinginformation graphically to users. The user interface may also be agraphic user interface as provided by, with, and/or atop operatingsystems and/or operating environments such as already discussed.

Cryptographic Server

A cryptographic server component 762 is a stored program component thatis executed by a CPU 716, cryptographic processor 742, cryptographicprocessor interface 728, cryptographic processor device 731, and/or thelike, to enable encryption schemes allowing for the secure transmissionof information across a communications network to enable the PPS.components to engage in secure transactions. The cryptographic server762 facilitates the secure accessing of resources on the PPS andfacilitates the access of secured resources on remote systems; i.e., itmay act as a client and/or server of secured resources. Cryptographicprocessor interfaces 728 can allow for expedition of encryption and/ordecryption requests by the cryptographic component. The cryptographiccomponent allows for the encryption and/or decryption of provided data.The cryptographic component allows for both symmetric and asymmetric(e.g., Pretty Good Protection (PGP)) encryption and/or decryption. Thecryptographic component may employ cryptographic techniques such as, butnot limited to: digital certificates (e.g., X.509 authenticationframework), digital signatures, dual signatures, enveloping, passwordaccess protection, public key management, and/or the like. Thecryptographic component will facilitate numerous (encryption and/ordecryption) security protocols such as, but not limited to: checksum,Data Encryption Standard (DES), Elliptical Curve Encryption (ECC),International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5,which is a one way hash operation), passwords, Secure Socket Layer(SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like.Employing such encryption security protocols, the PPS 700 may encryptall incoming and/or outgoing communications.

The PPS 700 may be associated with a secure enclave unit (not shown)that may represent any logic, circuitry, hardware, or other structuresfor creating and maintaining a secured, protected, or isolatedenvironment, in which an application or other software may run, execute,be loaded, or otherwise be present an information processing system. Thesecure enclave unit may further include encryption unit (not shown),which may include any logic, circuitry, or other hardware to execute anyone or more encryption algorithms and the corresponding decryptionalgorithms, and may include logic, circuitry, or other hardware sharedwith another encryption unit in processor. In one embodiment, the secureenclave unit includes the digital signatures, and biometric paymentinstruments created thereof.

Database

The database component 750 may be a fault tolerant, relational,scalable, secure database, such as Oracle or Sybase. Alternatively, thedatabase 750 may be implemented using various data-structures, such asan array, hash, (linked) list, struct, structured text file (e.g., XML),table, and/or the like. Such data-structures may be stored in memoryand/or in structured files. In another alternative, an object-orienteddatabase may be used. Also, the database may be implemented as a mix ofdata structures, objects, and relational structures.

In one embodiment, the database 750 includes several data tables 750A-E.A transaction data table 750A includes fields such as, but not limitedto: transaction information, service code, POS entry code, CVV, CVV2,limit to authorization, value of gift card, and/or the like. A tipdeterminant table 750B includes fields such as, but not limited to:merchant, customer, item type, item count, item expiration, card type,card value, location coordinates, tipping profile, tipping behavior,historical data, fingerprint, and the like. A condition 750C includesfields such as, but not limited to: location coordinates, connectionstatus, communication channel, open communication port, time of day,exception, and the like. An alert data table 750D includes fields suchas, but not limited to: receipt generated, engagement received, feedbackreceived, etc. An other data table 750E includes fields such as, but notlimited to: authorization flag, rejection flag, and the like.

In one embodiment, specific tables may be created when each of thecomponents are executed. Furthermore, the tables may be storedtemporarily or permanently in the database 750.

Components

The component(s) 748 is a stored program component that is executed bythe CPU 716. In one embodiment, the PPS component 748 incorporates anyand/or all combinations of the aspects of the PPS 700 that was discussedin the previous figures. As such, the PPS 700 affects accessing,obtaining and the provision of information, services, transactions,and/or the like across various communications networks.

Examples of components include, but are not limited to, dynamic tipgeneration component(s) 764, Authorization component(s) 766, POScomponent(s) 768, location component 770, pattern recognition component771, exception handling Component 772, mapping component(s) 774, andother component(s) 776. The dynamic tip generation component 764receives data from POS terminals and determines based on tipdeterminants what should the value of adaptive tip be. The authorizationcomponent 766 may allow and enable the PPS 700 to accept the paymentinstruments and authorize payment transactions. The POS component 768may allow and enable the PPS 700 to accept payment object data, e.g.,from the credit card or NFC based payment methods, and process ortransfer the transaction data to an external server, such as a paymentprocessing system and financial network system, to obtain financialaccount information of users to fulfill a transaction. The locationcomponent(s) 770 tracks the user's mobile device and the merchant pointof sale device to push information based on proximity through forexample, short-range communication networks, such as Bluetooth, BLE, andNFC technologies. The pattern recognition component 771 allows andenables the PPS 700 to analyze the data corresponding to tipdeterminants and generate tipping profiles and map relationships betweenbuyer and seller.

The exception handler component 772 detects any exceptions as per theconditions set by the customer or the merchant. For example, thecustomer may set the condition to override the dynamic tip at aparticular merchant location or time of the day.

The mapping component(s) 774 may allow and enable the PPS 700 to map thetipping profiles to merchants, buyers, merchant locations, item types orpayment objects.

The structure and/or operation of any of the PPS 700 components may becombined, consolidated, and/or distributed in any number of ways tofacilitate development and/or deployment. To this end, one may integratethe components into a common code base or in a facility that candynamically load the components on demand in an integrated fashion. Thecomponents may be consolidated and/or distributed in countlessvariations through standard data processing and/or developmenttechniques. Multiple instances of any one of the program components maybe instantiated on a single node, and/or across numerous nodes toimprove performance through load-balancing and/or data-processingtechniques. Furthermore, single instances may also be distributed acrossmultiple controllers and/or storage devices; e.g., databases.

If component collection components are discrete, separate, and/orexternal to one another, then communicating, obtaining, and/or providingdata with and/or to other component components may be accomplishedthrough inter-application data processing communication techniques suchas, but not limited to: Application Program Interfaces (API) informationpassage; (distributed) Component Object Model ((D)COM), (Distributed)Object Linking and Embedding ((D)OLE), and/or the like), Common ObjectRequest Broker Architecture (CORBA), SOAP, process pipes, shared files,and/or the like. Messages sent between discrete component components forinter-application communication or within memory spaces of a singularcomponent for intra-application communication may be facilitated throughthe creation and parsing of a grammar. A grammar may be developed byusing development tools such as lex, yacc, XML, and/or the like, whichallow for grammar generation and parsing capabilities, which in turn mayform the basis of communication messages within and between components.The grammar syntax itself may be presented as structured data that isinterpreted and/or otherwise used to generate the parsing mechanism.Also, once the parsing mechanism is generated and/or instantiated, ititself may process and/or parse structured data such as, but not limitedto: character (e.g., tab) delineated text, HTML, structured textstreams, XML, and/or the like structured data. In another embodiment,inter-application data processing protocols themselves may haveintegrated and/or readily available parsers (e.g., SOAP, and/or likeparsers) that may be employed to parse (e.g., communications) data.Further, the parsing grammar may be used beyond message parsing, but mayalso be used to parse: databases, data collections, data stores,structured data, and/or the like. Again, the desired configuration willdepend upon the context, environment, and requirements of systemdeployment.

Regarding the processes 200 and 600 while the various steps, blocks orsub-processes are presented in a given order, alternative embodimentscan perform routines having steps, or employ systems having steps,blocks or sub-processes, in a different order, and some steps,sub-processes or blocks can be deleted, moved, added, subdivided,combined, and/or modified to provide alternative or sub-combinations.Each of these steps, blocks or sub-processes can be implemented in avariety of different ways. Also, while steps, sub-processes or blocksare at times shown as being performed in series, some steps,sub-processes or blocks can instead be performed in parallel, or can beperformed at different times as will be recognized by a person ofordinary skill in the art. Further, any specific numbers noted hereinare only examples; alternative implementations can employ differingvalues or ranges.

While aspects of the described subject matter can be implemented in anynumber of different systems, circuitries, environments, and/orconfigurations, the embodiments are described in the context of thefollowing exemplary system(s) and configuration(s). The descriptions anddetails of well-known components are omitted for simplicity of thedescription. It will thus be appreciated that those skilled in the artwill be able to devise various arrangements that, although notexplicitly described or shown herein, embody the principles of thepresent subject matter. Furthermore, all examples recited herein areintended to be for illustrative purposes only to aid the reader inunderstanding the principles of the present subject matter and theconcepts contributed by the inventor(s) to furthering the art, and areto be construed as being without limitation to such specifically recitedexamples and conditions. Moreover, all statements herein recitingprinciples, aspects, and embodiments of the present subject matter, aswell as specific examples thereof, are intended to encompass equivalentsthereof. Some recurring terms are now described. These definitionsshould not be considered limiting.

It should also be appreciated by those skilled in the art that any blockdiagrams, steps, or sub-processes herein represent conceptual views ofillustrative systems embodying the principles of the present subjectmatter. Similarly, it will be appreciated that any flow charts, flowdiagrams, state transition diagrams, pseudo code, and the like representvarious processes which may be substantially represented in computerreadable medium and so executed by a computer or processor, whether ornot such computer or processor is explicitly shown. The order in whichthe methods are described are not intended to be construed as alimitation, and any number of the described method blocks can bedeleted, moved, added, subdivided, combined, and/or modified in anyorder to implement the methods, or an alternative combination orsub-combinations. Also, while steps, sub-processes or blocks are attimes shown as being performed in series, some steps, sub-processes orblocks can instead be performed in parallel, or can be performed atdifferent times as will be recognized by a person of ordinary skill inthe art. Further any specific numbers noted herein are only examples;alternative implementations can employ differing values or ranges.Furthermore, the methods can be implemented in any suitable hardware,software, firmware, or combination thereof.

Reference to an “embodiment” in this document does not limit thedescribed elements to a single embodiment; all described elements may becombined in any embodiment in any number of ways. Furthermore, for thepurposes of interpreting this specification, the use of “or” hereinmeans “and/or” unless stated otherwise. The use of “a” or “an” hereinmeans “one or more” unless stated otherwise. The use of “comprise,”“comprises,” “comprising,” “include,” “includes,” and “including” areinterchangeable and not intended to be limiting. Also, unless otherwisestated, the use of the terms such as “first,” “second,” “third,”“upper,” “lower,” and the like do not denote any spatial, sequential, orhierarchical order or importance, but are used to distinguish oneelement from another. It is to be appreciated that the use of the terms“and/or” and “at least one of”, for example, in the cases of “A and/orB” and “at least one of A and B”, is intended to encompass the selectionof the first listed option (A) only, or the selection of the secondlisted option (B) only, or the selection of both options (A and B). As afurther example, in the cases of “A, B, and/or C” and “at least one ofA, B, and C”, such phrasing is intended to encompass the selection ofthe first listed option (A) only, or the selection of the second listedoption (B) only, or the selection of the third listed option (C) only,or the selection of the first and the second listed options (A and B)only, or the selection of the first and third listed options (A and C)only, or the selection of the second and third listed options (B and C)only, or the selection of all three options (A and B and C). This may beextended, as readily apparent by one of ordinary skill in this andrelated arts, for as many items listed.

Additionally, note that the terms “connected” or “coupled” and relatedterms used throughout the description are used in an operational senseand are not necessarily limited to a direct physical connection orcoupling. Thus, for example, two devices may be coupled directly, or viaone or more intermediary media or devices. As another example, devicesmay be coupled in such a way that information can be passedthere-between, while not sharing any physical connection with oneanother. Based on the disclosure provided herein, one of ordinary skillin the art will appreciate a variety of ways in which connection orcoupling exists in accordance with the aforementioned definition.

The term “cause” and variations thereof, as used throughout thisdescription, refers to either direct causation or indirect causation.For example, a computer system can “cause” an action by sending amessage to a second computer system that commands, requests or promptsthe second computer system to perform the action. Any number ofintermediary devices may examine and/or relay the message during thisprocess. In this regard, a device can “cause” an action even though itmay not be known to the device whether the action will ultimately beexecuted or completed.

In some implementations, the network(s) may be any type of network knownin the art, such as a local area network or a wide area network, such asthe Internet, and may include a wireless network, such as a cellularnetwork, a cloud network, a local wireless network, such as Wi-Fi and/orclose-range wireless communications, such as Bluetooth® and Bluetooth®low energy, near field communications (NFC), a wired network, or anyother such network, or any combination thereof. Accordingly, the one ormore networks may include both wired and/or wireless communicationtechnologies, including Bluetooth®, Bluetooth® low energy, Wi-Fi andcellular communication technologies like worldwide interoperability formicrowave access (WiMAX), 3G, 4G, CDMA, digital subscriber line (DSL),etc., cloud computing technologies, as well as wired or fiber optictechnologies. Additionally, the communication network may be a meshnetwork. For example, in a wireless local area network (WLAN), networkdevices may be configured to receive and forward communications whichare ultimately destined for a different device. These types of networksare generically referred to as “mesh” networks, where network nodes mayform a “mesh” of paths for which communications may travel to reachtheir destination. Wireless networks may use beacon transmissions toadvertise the network's existence, as well as provide information aboutthe network and capabilities associated with the network. Differentkinds of beaconing mechanisms may be used, for example, one forinfrastructure mode networks (also called basic service set (BSS)networks) and one for ad-hoc mode networks (also called independentbasic service set (IBSS) networks). In infrastructure networks, accesspoints (APs) are the entities responsible for generating beacons whereasin ad hoc networks, all network nodes (including user stations)participate in the generation of beacons. The ad hoc network beacons(referred to as IBSS beacons) are used to advertise the network (whichconsists of all the nodes) as a whole while the infrastructure networkbeacons (referred to as BSS beacons) are generated by an AP and meant toadvertise the existence of only that individual AP. Components used forsuch communications can depend at least in part upon the type ofnetwork, the environment selected, or both. Protocols for communicatingover such networks are well known and are not discussed herein indetail.

The term “component,” “module” or “engine” refers broadly to general orspecific-purpose hardware, software, or firmware (or any combinationthereof) components. Components and engines are typically functionalcomponents that can generate useful data or other output using specifiedinput(s). A component or engine may or may not be self-contained.Depending upon implementation-specific or other considerations, thecomponents or engines may be centralized or functionally distributed. Anapplication program (also called an “application”) may include one ormore components and/or engines, or a component and/or engine can includeone or more application programs.

What is claimed is:
 1. A method comprising: sending, from an instance ofan application installed on a computing device associated with amerchant and to a payment processing service, transaction dataassociated with a payment transaction between the merchant and acustomer, the transaction data including at least one tip determinantassociated with an item purchased via the payment transaction;receiving, by the instance of the application and from the paymentprocessing service, instructions to generate a user interface associatedwith the payment transaction, wherein the user interface is associatedwith a digital receipt that is interactable to enable the customer toselect from one or more tip amounts; presenting, by the instance of theapplication, the user interface; receiving, by the instance of theapplication and via the user interface, a selection of a tip amount ofthe one or more tip amounts; and sending, from the instance of theapplication and to the payment processing service, the selection forpayment processing.
 2. The method of claim 1, wherein the one or moretip amounts are based at least in part on a tipping profile.
 3. Themethod of claim 1, wherein the user interface further comprises one ormore customer engagement interface components or one or more customertransaction interface components.
 4. The method of claim 3, wherein theone or more customer engagement interface components are available viathe digital receipt for a predefined time period.
 5. The method of claim1, wherein the user interface is presented at a time after the paymenttransaction is processed by the payment processing service.
 6. Themethod of claim 1, wherein the transaction data comprises dataassociated with a payment object presented by the customer for paymenttowards the payment transaction.
 7. The method of claim 1, furthercomprising: generating an interactive transaction record that isaccessible via the user interface, the interactive transaction recordcomprising a plurality of transaction records completed between thecustomer and the merchant; and updating the interactive transactionrecord for a new user interface generated for a new payment transactionbetween the customer and the merchant.
 8. The method of claim 1, whereinthe user interface further comprises an interactive tipping componentthat is associated with a transaction timeframe that defines a timeperiod for the customer to select the one or more tip amounts using theinteractive tipping component.
 9. The method of claim 8, wherein anominal amount configured by the customer is automatically authorized asa default tip when no selection of one of the one or more tip amounts isreceived within the transaction timeframe.
 10. A system comprising: amemory; one or more processors to execute instructions stored in thememory for: send, from a first application installed on a computingdevice associated with a merchant and to a payment processing service,transaction data associated with a payment transaction between themerchant and a customer; receive, by a second application executing on acustomer device and from the payment processing service, instructions togenerate a user interface associated with the payment transaction;present, by the second application, the user interface; receive, via theuser interface, a selection of a tip amount; and send, to the paymentprocessing service, the selection for payment processing.
 11. The systemof claim 10, wherein the transaction data comprises at least one tipdeterminant associated with an item purchased via the paymenttransaction.
 12. The system of claim 10, wherein the user interface isassociated with a digital receipt that is interactable to enable thecustomer to select from one or more tip amounts.
 13. The system of claim12, wherein the user interface further comprises one or more customerengagement interface components or one or more customer transactioninterface components.
 14. The system of claim 13, wherein the one ormore customer engagement interface components are available via thedigital receipt for a predefined time period.
 15. The system of claim10, wherein the user interface is presented at a time after the paymenttransaction is processed by the payment processing service.
 16. One ormore non-transitory computer-readable media maintaining instructionsstored in a memory that, when executed by one or more processors,program the one or more processors to perform acts comprising:receiving, by an application executing on a customer device of acustomer and from a payment processing service, instructions to generatea user interface associated with a payment transaction; presenting, bythe application, the user interface; receiving, via the user interface,a selection of a tip amount; and sending, to the payment processingservice, the selection for payment processing.
 17. The one or morenon-transitory computer readable media of claim 16, wherein the userinterface further comprises an interactive tipping component that isassociated with a transaction timeframe that defines a time period forthe customer to select one or more tip amounts using the interactivetipping component.
 18. The one or more non-transitory computer readablemedia of claim 17, wherein a nominal amount configured by the customeris automatically authorized as a default tip when no selection of one ofthe one or more tip amounts is received within the transactiontimeframe.
 19. The one or more non-transitory computer readable media ofclaim 16, wherein the user interface is associated with a digitalreceipt that is interactable to enable the customer to select from oneor more tip amounts.
 20. The one or more non-transitory computerreadable media of claim 16, wherein the user interface further comprisesone or more customer engagement interface components or one or morecustomer transaction interface components.